[bugzilla-daemon@xxxxxxxxxxxxx]

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

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit f635efb6a63e10c03713cfae75490dda7cd1092e
Author: Guy Harris <guy@alum.mit.edu>
Date:   Fri May 23 14:03:42 2014 -0700

    More checks for the presence of a time stamp.

    And make sure we have a pointer to the struct wtap_pkthdr for the packet
    before we check it for a time stamp.

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


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

==17541== Memcheck, a memory error detector
==17541== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==17541== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==17541== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-25-6756.pcap
==17541== 
==17541== 
==17541== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==17541==    at 0x65B143A: ep_verify_pointer (emem.c:606)
==17541==    by 0x65AD23B: col_set_str (column-utils.c:528)
==17541==    by 0x6C04E21: dissect_sctp (packet-sctp.c:4487)
==17541==    by 0x65BC787: call_dissector_through_handle (packet.c:596)
==17541==    by 0x65BD1ED: call_dissector_work (packet.c:683)
==17541==    by 0x65BDA12: dissector_try_uint_new (packet.c:1114)
==17541==    by 0x6978BF1: dissect_ip (packet-ip.c:2409)
==17541==    by 0x65BC787: call_dissector_through_handle (packet.c:596)
==17541==    by 0x65BD1ED: call_dissector_work (packet.c:683)
==17541==    by 0x65BDA12: dissector_try_uint_new (packet.c:1114)
==17541==    by 0x65BDA66: dissector_try_uint (packet.c:1140)
==17541==    by 0x6841E95: dissect_ethertype (packet-ethertype.c:303)
==17541== 
==17541== HEAP SUMMARY:
==17541==     in use at exit: 30,902,343 bytes in 426,555 blocks
==17541==   total heap usage: 55,069,712 allocs, 54,643,157 frees,
3,813,744,739 bytes allocated
==17541== 
==17541== LEAK SUMMARY:
==17541==    definitely lost: 304 bytes in 22 blocks
==17541==    indirectly lost: 8 bytes in 1 blocks
==17541==      possibly lost: 0 bytes in 0 blocks
==17541==    still reachable: 30,902,031 bytes in 426,532 blocks
==17541==         suppressed: 0 bytes in 0 blocks
==17541== Rerun with --leak-check=full to see details of leaked memory
==17541== 
==17541== For counts of detected and suppressed errors, rerun with: -v
==17541== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 51 from 5)
./tools/valgrind-wireshark.sh: line 113: 17541 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.