Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9702] New: Buildbot crash output: fuzz-2014-01-26-2269.pcap

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9702
Summary	Buildbot crash output: fuzz-2014-01-26-2269.pcap
Classification	Unclassified
Product	Wireshark
Version	unspecified
Hardware	x86-64
URL	http://www.wireshark.org/download/automated/captures/fuzz-2014-01-26-2269.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-01-26-2269.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/10860-packet-gsm.pcap

Build host information:
Linux wsbb04 3.2.0-58-generic #88-Ubuntu SMP Tue Dec 3 17:37:58 UTC 2013 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=https://code.wireshark.org/review/wireshark
BUILDBOT_BUILDNUMBER=2534
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang-Code-Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=2fa2515f77a0604586612234ebf3e6f89759bf4a

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 2fa2515f77a0604586612234ebf3e6f89759bf4a
Author: Guy Harris <guy@alum.mit.edu>
Date:   Fri Jan 24 07:55:03 2014 +0000

    Check for a zero offset in the "get status" reply *before* adding the
    offset in the tvbuff of the beginning of the packet to it.  Otherwise,
    it will never be zero, and the tests will always think the field pointed
    to by the offset is present.

    svn path=/trunk/; revision=54938


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

==14413== Memcheck, a memory error detector
==14413== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==14413== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==14413== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-01-26-2269.pcap
==14413== 
**
ERROR:packet.c:2208:call_dissector_only: assertion failed: (handle != NULL)
==14413== 
==14413== HEAP SUMMARY:
==14413==     in use at exit: 17,706,334 bytes in 463,260 blocks
==14413==   total heap usage: 930,021 allocs, 466,761 frees, 50,578,807 bytes
allocated
==14413== 
==14413== LEAK SUMMARY:
==14413==    definitely lost: 2,071 bytes in 26 blocks
==14413==    indirectly lost: 8 bytes in 1 blocks
==14413==      possibly lost: 0 bytes in 0 blocks
==14413==    still reachable: 17,704,255 bytes in 463,233 blocks
==14413==         suppressed: 0 bytes in 0 blocks
==14413== Rerun with --leak-check=full to see details of leaked memory
==14413== 
==14413== For counts of detected and suppressed errors, rerun with: -v
==14413== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 3)
./tools/valgrind-wireshark.sh: line 109: 14413 Aborted                 (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.