Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 10021] New: Buildbot crash output: fuzz-2014-04-20-7766.pc

Date: Tue, 22 Apr 2014 17:30:10 +0000
Bug ID 10021
Summary Buildbot crash output: fuzz-2014-04-20-7766.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-20-7766.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-20-7766.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/jxta-mcast-sample.pcap

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=2705
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=6c6aeb1841a7cd65e77e8729dde4e7ba25e327ad

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 6c6aeb1841a7cd65e77e8729dde4e7ba25e327ad
Author: Guy Harris <[email protected]>
Date:   Sun Apr 20 17:47:59 2014 -0700

    Fix various white space issues and typoes and regenerate SABP dissector.

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


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


***MEMORY-ERROR***: [31896]: GSlice: failed to allocate 1008 bytes (alignment:
1024): Cannot allocate memory


[ no debug trace ]


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