Wireshark-bugs: [Wireshark-bugs] [Bug 9967] New: Buildbot crash output: fuzz-2014-04-08-30757.pc

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 09 Apr 2014 20:30:33 +0000
Bug ID 9967
Summary Buildbot crash output: fuzz-2014-04-08-30757.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-08-30757.pcap
OS Ubuntu
Status CONFIRMED
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected] 

Problems have been found with the following capture file:

http://www.wireshark.org/download/automated/captures/fuzz-2014-04-08-30757.pcap

stderr:
Input file:
/home/wireshark/menagerie/menagerie/12531-lbtru-loss-validation.pcapng.gz

Build host information:
Linux wsbb04 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 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://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=2674
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=6ae5747c098db1cbeeb890da5b5386ecaed6d55b

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 6ae5747c098db1cbeeb890da5b5386ecaed6d55b
Author: Guy Harris <[email protected]>
Date:   Tue Apr 8 12:25:49 2014 -0700

    I don't see anything here requiring netinet/in.h, so don't include it.

    Change-Id: Id024d7e2529a6eb9ca79ce8c3ea674a3c0795b85
    Reviewed-on: https://code.wireshark.org/review/1030
    Reviewed-by: Guy Harris <[email protected]>


Command and args:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-nVxr


***MEMORY-ERROR***: [23637]: GSlice: MemChecker: failure in debugging tree:
Cannot allocate memory

[ no debug trace ]

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