Wireshark-bugs: [Wireshark-bugs] [Bug 10146] New: Buildbot crash output: fuzz-2014-05-30-8024.pc
Date: Fri, 30 May 2014 18:50:05 +0000
Bug ID 10146
Summary Buildbot crash output: fuzz-2014-05-30-8024.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-05-30-8024.pcap
OS Ubuntu
Status CONFIRMED
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter buildbot-do-not-reply@wireshark.org

Problems have been found with the following capture file:

http://www.wireshark.org/download/automated/captures/fuzz-2014-05-30-8024.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/1598-ws_00445_20080327094342.gz

Build host information:
Linux wsbb04 3.2.0-61-generic #93-Ubuntu SMP Fri May 2 21:31:50 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 12.04.4 LTS
Release:    12.04
Codename:    precise

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=2775
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=88a64b9e2b1e39c643277edeb4c4ae969a0b39a5

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 88a64b9e2b1e39c643277edeb4c4ae969a0b39a5
Author: Richard Sharpe <realrichardsharpe@gmail.com>
Date:   Mon May 26 16:05:36 2014 -0700

    Improve the fix by removing code that miss dissects SPNEGO stuff ... as
well
    as remove redundant stuff from the spnego.cnf file.

    Signed-off-by: Richard Sharpe <realrichardsharpe@gmail.com>
    Change-Id: I90a962a39dc4da0f13055c9b3893c26044f1fc97
    Reviewed-on: https://code.wireshark.org/review/1809
    Reviewed-by: Tomáš Kukosa <tomas.kukosa@unify.com>
    Reviewed-by: Michael Mann <mmann78@netscape.net>


Command and args: ./tools/valgrind-wireshark.sh -T

==20588== Memcheck, a memory error detector
==20588== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==20588== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==20588== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-30-8024.pcap
==20588== 
==20588== 
==20588== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==20588==    at 0xA5B403E: __write_nocancel (syscall-template.S:82)
==20588==    by 0xA546882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==20588==    by 0xA546749: new_do_write (fileops.c:543)
==20588==    by 0xA547EB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==20588==    by 0xA547024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==20588==    by 0xA53CCDC: fwrite (iofwrite.c:45)
==20588==    by 0x65C79AD: print_line_text (print.c:1143)
==20588==    by 0x65C9652: proto_tree_print_node (print.c:192)
==20588==    by 0x65CB18B: proto_tree_children_foreach (proto.c:629)
==20588==    by 0x65C971D: proto_tree_print_node (print.c:241)
==20588==    by 0x65CB18B: proto_tree_children_foreach (proto.c:629)
==20588==    by 0x65C87E5: proto_tree_print (print.c:153)
==20588== 
==20588== HEAP SUMMARY:
==20588==     in use at exit: 30,857,008 bytes in 425,344 blocks
==20588==   total heap usage: 54,895,574 allocs, 54,470,230 frees,
3,802,136,167 bytes allocated
==20588== 
==20588== LEAK SUMMARY:
==20588==    definitely lost: 304 bytes in 22 blocks
==20588==    indirectly lost: 8 bytes in 1 blocks
==20588==      possibly lost: 0 bytes in 0 blocks
==20588==    still reachable: 30,856,696 bytes in 425,321 blocks
==20588==         suppressed: 0 bytes in 0 blocks
==20588== Rerun with --leak-check=full to see details of leaked memory
==20588== 
==20588== For counts of detected and suppressed errors, rerun with: -v
==20588== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 55 from 5)
./tools/valgrind-wireshark.sh: line 113: 20588 CPU time limit exceeded (core
dumped) $LIBTOOL valgrind --suppressions=`dirname $0`/vg-suppressions
--tool=$TOOL $CALLGRIND_OUT_FILE $VERBOSE $LEAK_CHECK $REACHABLE $TRACK_ORIGINS
$COMMAND $COMMAND_ARGS $PCAP $COMMAND_ARGS2 > /dev/null

[ no debug trace ]


You are receiving this mail because:
  • You are watching all bug changes.