Wireshark-bugs: [Wireshark-bugs] [Bug 10112] New: Buildbot crash output: fuzz-2014-05-16-5359.pc

Date: Sat, 17 May 2014 06:20:07 +0000
Bug ID 10112
Summary Buildbot crash output: fuzz-2014-05-16-5359.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-05-16-5359.pcap
OS Ubuntu
Status CONFIRMED
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Problems have been found with the following capture file:

http://www.wireshark.org/download/automated/captures/fuzz-2014-05-16-5359.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://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=2761
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=773c02da8f06298072d2f0b7d211b54d70ec226c

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 773c02da8f06298072d2f0b7d211b54d70ec226c
Author: Masayuki Takemura <[email protected]>
Date:   Thu May 15 22:37:37 2014 +0900

    diameter_3gpp: Dissect Feature-List flags in Gx message

    With this patch, wireshark dissects the Feature-List flags field in Gx
message
    and displays the name and value of each of Feature bit.

    Change-Id: I18af8a133ae7db4da5a126a81521c474d1553719
    Reference: 3GPP TS 29.212 V11.7.0, Section 5.4.1.
    Reviewed-on: https://code.wireshark.org/review/1652
    Reviewed-by: Anders Broman <[email protected]>


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

==16631== Memcheck, a memory error detector
==16631== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==16631== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==16631== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-16-5359.pcap
==16631== 
==16631== 
==16631== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==16631==    at 0xA5A003E: __write_nocancel (syscall-template.S:82)
==16631==    by 0xA532882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==16631==    by 0xA532749: new_do_write (fileops.c:543)
==16631==    by 0xA533EB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==16631==    by 0xA533024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==16631==    by 0xA5285EC: fputs (iofputs.c:42)
==16631==    by 0x65C0034: print_line_text (print.c:1159)
==16631==    by 0x65C1CE2: proto_tree_print_node (print.c:192)
==16631==    by 0x65C383B: proto_tree_children_foreach (proto.c:629)
==16631==    by 0x65C1DAD: proto_tree_print_node (print.c:241)
==16631==    by 0x65C383B: proto_tree_children_foreach (proto.c:629)
==16631==    by 0x65C1DAD: proto_tree_print_node (print.c:241)
==16631== 
==16631== HEAP SUMMARY:
==16631==     in use at exit: 30,109,595 bytes in 419,279 blocks
==16631==   total heap usage: 53,918,231 allocs, 53,498,952 frees,
3,731,490,422 bytes allocated
==16631== 
==16631== LEAK SUMMARY:
==16631==    definitely lost: 304 bytes in 22 blocks
==16631==    indirectly lost: 8 bytes in 1 blocks
==16631==      possibly lost: 0 bytes in 0 blocks
==16631==    still reachable: 30,109,283 bytes in 419,256 blocks
==16631==         suppressed: 0 bytes in 0 blocks
==16631== Rerun with --leak-check=full to see details of leaked memory
==16631== 
==16631== For counts of detected and suppressed errors, rerun with: -v
==16631== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 61 from 5)
./tools/valgrind-wireshark.sh: line 113: 16631 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.