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 9975] New: Buildbot crash output: fuzz-2014-04-08-3297.pca

Date: Wed, 09 Apr 2014 20:31:13 +0000
Bug ID 9975
Summary Buildbot crash output: fuzz-2014-04-08-3297.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-08-3297.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-3297.pcap

stderr:
Input file:
/home/wireshark/menagerie/menagerie/11952-group_stats_desc_feats.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=2676
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=130b94fa61baf82f4de5e5625c332de690210eba

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 130b94fa61baf82f4de5e5625c332de690210eba
Author: Guy Harris <[email protected]>
Date:   Tue Apr 8 19:01:59 2014 -0700

    Sadly, packet-dcerpc-mapi.c is not yet free of warnings.

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


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


(process:30714): GLib-ERROR (recursed) **:
/build/buildd/glib2.0-2.32.4/./glib/gmem.c:230: failed to allocate 4 bytes
[ no debug trace ]


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