Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 10127] New: Buildbot crash output: fuzz-2014-05-21-5755.pcap

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	10127
Summary	Buildbot crash output: fuzz-2014-05-21-5755.pcap
Classification	Unclassified
Product	Wireshark
Version	unspecified
Hardware	x86-64
URL	http://www.wireshark.org/download/automated/captures/fuzz-2014-05-21-5755.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-21-5755.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=2764
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=eef176df4eac066e02a738654097848c57880d5c

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit eef176df4eac066e02a738654097848c57880d5c
Author: Mark Weel <markweel@hotmail.com>
Date:   Mon May 19 16:10:50 2014 +0200

    DIS: update enumerations to SISO-REF-010-00v20-0

    Change-Id: I99cd075bef5b8d3f2546032cc6ce9774bcf8efc1
    Reviewed-on: https://code.wireshark.org/review/1695
    Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com>
    Reviewed-by: Anders Broman <a.broman58@gmail.com>


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

==32157== Memcheck, a memory error detector
==32157== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==32157== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==32157== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-21-5755.pcap
==32157== 
==32157== 
==32157== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==32157==    at 0xA5A803E: __write_nocancel (syscall-template.S:82)
==32157==    by 0xA53A882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==32157==    by 0xA53A749: new_do_write (fileops.c:543)
==32157==    by 0xA53BEB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==32157==    by 0xA53B024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==32157==    by 0xA5305EC: fputs (iofputs.c:42)
==32157==    by 0x65C3C44: print_line_text (print.c:1145)
==32157==    by 0x65C58C2: proto_tree_print_node (print.c:192)
==32157==    by 0x65C73FB: proto_tree_children_foreach (proto.c:629)
==32157==    by 0x65C598D: proto_tree_print_node (print.c:241)
==32157==    by 0x65C73FB: proto_tree_children_foreach (proto.c:629)
==32157==    by 0x65C4A55: proto_tree_print (print.c:153)
==32157== 
==32157== HEAP SUMMARY:
==32157==     in use at exit: 30,711,706 bytes in 420,189 blocks
==32157==   total heap usage: 54,070,302 allocs, 53,650,113 frees,
3,743,917,707 bytes allocated
==32157== 
==32157== LEAK SUMMARY:
==32157==    definitely lost: 304 bytes in 22 blocks
==32157==    indirectly lost: 8 bytes in 1 blocks
==32157==      possibly lost: 0 bytes in 0 blocks
==32157==    still reachable: 30,711,394 bytes in 420,166 blocks
==32157==         suppressed: 0 bytes in 0 blocks
==32157== Rerun with --leak-check=full to see details of leaked memory
==32157== 
==32157== For counts of detected and suppressed errors, rerun with: -v
==32157== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 63 from 5)
./tools/valgrind-wireshark.sh: line 113: 32157 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.