Wireshark-bugs: [Wireshark-bugs] [Bug 10157] New: Buildbot crash output: fuzz-2014-06-01-27465.p
Date: Mon, 02 Jun 2014 01:30:05 +0000
Bug ID 10157
Summary Buildbot crash output: fuzz-2014-06-01-27465.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-06-01-27465.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-06-01-27465.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=2783
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=799972425dc2178b28067e729abc99d31e0ccc67

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 799972425dc2178b28067e729abc99d31e0ccc67
Author: Guy Harris <guy@alum.mit.edu>
Date:   Sat May 31 02:27:31 2014 -0700

    We need a "wlan_datapad" dissector as well.

    Change-Id: I8d7e0ebeef2a912737b3afc08fcaf166dfb525b1
    Reviewed-on: https://code.wireshark.org/review/1895
    Reviewed-by: Guy Harris <guy@alum.mit.edu>


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

==28426== Memcheck, a memory error detector
==28426== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==28426== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==28426== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-06-01-27465.pcap
==28426== 
==28426== 
==28426== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==28426==    at 0x98E5A9A: g_strlcpy (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.4)
==28426==    by 0x70F6E42: wmem_strbuf_append (wmem_strbuf.c:152)
==28426==    by 0x6878A86: dissect_frame (packet-frame.c:567)
==28426==    by 0x65BF9F7: call_dissector_through_handle (packet.c:626)
==28426==    by 0x65C047D: call_dissector_work (packet.c:713)
==28426==    by 0x65C23E0: call_dissector_with_data (packet.c:2295)
==28426==    by 0x65C2B2D: dissect_record (packet.c:497)
==28426==    by 0x65B5801: epan_dissect_run_with_taps (epan.c:350)
==28426==    by 0x414199: process_packet (tshark.c:3537)
==28426==    by 0x40BFC9: main (tshark.c:3327)
==28426== 
==28426== HEAP SUMMARY:
==28426==     in use at exit: 30,825,286 bytes in 424,029 blocks
==28426==   total heap usage: 54,719,368 allocs, 54,295,339 frees,
3,790,571,264 bytes allocated
==28426== 
==28426== LEAK SUMMARY:
==28426==    definitely lost: 304 bytes in 22 blocks
==28426==    indirectly lost: 8 bytes in 1 blocks
==28426==      possibly lost: 0 bytes in 0 blocks
==28426==    still reachable: 30,824,974 bytes in 424,006 blocks
==28426==         suppressed: 0 bytes in 0 blocks
==28426== Rerun with --leak-check=full to see details of leaked memory
==28426== 
==28426== For counts of detected and suppressed errors, rerun with: -v
==28426== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 99 from 5)
./tools/valgrind-wireshark.sh: line 113: 28426 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.