Wireshark-bugs: [Wireshark-bugs] [Bug 13243] New: Buildbot crash output: fuzz-2016-12-12-16393.p
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 13 Dec 2016 06:00:07 +0000
Bug ID 13243
Summary Buildbot crash output: fuzz-2016-12-12-16393.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-12-12-16393.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-16393.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=174
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=13b230fd05225e243e2a20be402c1e454e002b55

Return value:  152

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 13b230fd05225e243e2a20be402c1e454e002b55
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/19196


==26450== Memcheck, a memory error detector
==26450== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==26450== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==26450== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -Vx -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-12-12-16393.pcap
==26450== 
==26450== 
==26450== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==26450==    at 0xA3091BA: ??? (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
==26450==    by 0xA30A102: g_hash_table_remove_all (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
==26450==    by 0xA30A13D: g_hash_table_destroy (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
==26450==    by 0x69569E6: proto_cleanup (proto.c:567)
==26450==    by 0x6939DAD: epan_cleanup (epan.c:165)
==26450==    by 0x40E0C7: main (tshark.c:2045)
==26450== 
==26450== HEAP SUMMARY:
==26450==     in use at exit: 37,152,453 bytes in 230,379 blocks
==26450==   total heap usage: 72,252,245 allocs, 72,021,866 frees,
5,453,606,354 bytes allocated
==26450== 
==26450== LEAK SUMMARY:
==26450==    definitely lost: 1,084,437 bytes in 2,199 blocks
==26450==    indirectly lost: 37,823 bytes in 2,108 blocks
==26450==      possibly lost: 4,194,304 bytes in 2 blocks
==26450==    still reachable: 31,835,889 bytes in 226,070 blocks
==26450==         suppressed: 0 bytes in 0 blocks
==26450== Rerun with --leak-check=full to see details of leaked memory
==26450== 
==26450== For counts of detected and suppressed errors, rerun with: -v
==26450== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
./tools/valgrind-wireshark.sh: line 123: 26450 CPU time limit exceeded (core
dumped) $cmdline > /dev/null

[ no debug trace ]

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