Wireshark-bugs: [Wireshark-bugs] [Bug 13247] New: Buildbot crash output: fuzz-2016-12-12-29678.p
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 14 Dec 2016 10:50:07 +0000
Bug ID 13247
Summary Buildbot crash output: fuzz-2016-12-12-29678.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-12-12-29678.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:

https://www.wireshark.org/download/automated/captures/fuzz-2016-12-12-29678.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/SMB-locking.pcapng.gz

Build host information:
Linux wsbb04 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:    16.04
Codename:    xenial

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=238
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.0/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=7ed3dc3f7aa4ff2081cc83fa84f14f2981ac9373

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 7ed3dc3f7aa4ff2081cc83fa84f14f2981ac9373
Author: Guy Harris <guy@alum.mit.edu>
Date:   Sat Dec 10 10:37:07 2016 -0800

    Initialize fd_head->frame in all cases where we allocate fd_head.

    Also, sort the initializations of structure members by the order in the
    structure, to make it easier to check that we've initialized them all.

    Bug: 13231
    Change-Id: Id2819940d916a5fd5a3f1bf2fc20bd3ee34a75f4
    Reviewed-on: https://code.wireshark.org/review/19195
    Reviewed-by: Guy Harris <guy@alum.mit.edu>
    (cherry picked from commit 2dfa603333416aec69719fb074388886f0fc96b2)
    Reviewed-on: https://code.wireshark.org/review/19197


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

==2140== Memcheck, a memory error detector
==2140== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==2140== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==2140== Command:
/home/wireshark/builders/wireshark-2.0-fuzz/fuzztest/install/bin/tshark -Vx -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.0/fuzz-2016-12-12-29678.pcap
==2140== 
==2140== 
==2140== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==2140==    at 0x9FC8178: ??? (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
==2140==    by 0x9FC9102: g_hash_table_remove_all (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
==2140==    by 0x9FC913D: g_hash_table_destroy (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
==2140==    by 0x6866A16: proto_cleanup (proto.c:536)
==2140==    by 0x684AF5D: epan_cleanup (epan.c:133)
==2140==    by 0x40CDA0: main (tshark.c:2354)
==2140== 
==2140== HEAP SUMMARY:
==2140==     in use at exit: 35,606,199 bytes in 198,891 blocks
==2140==   total heap usage: 73,287,154 allocs, 73,088,263 frees, 5,498,731,732
bytes allocated
==2140== 
==2140== LEAK SUMMARY:
==2140==    definitely lost: 33,619 bytes in 2,106 blocks
==2140==    indirectly lost: 28,400 bytes in 1,775 blocks
==2140==      possibly lost: 5,242,880 bytes in 3 blocks
==2140==    still reachable: 30,301,300 bytes in 195,007 blocks
==2140==         suppressed: 0 bytes in 0 blocks
==2140== Rerun with --leak-check=full to see details of leaked memory
==2140== 
==2140== For counts of detected and suppressed errors, rerun with: -v
==2140== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
./tools/valgrind-wireshark.sh: line 113:  2140 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.