Wireshark-bugs: [Wireshark-bugs] [Bug 9979] New: Buildbot crash output: fuzz-2014-04-09-32547.pc
Date: Thu, 10 Apr 2014 10:40:04 +0000
Bug ID 9979
Summary Buildbot crash output: fuzz-2014-04-09-32547.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-09-32547.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-04-09-32547.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://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=2684
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=7cbc790832cfb067857b523ef2ad440966ef824a

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 7cbc790832cfb067857b523ef2ad440966ef824a
Author: Guy Harris <guy@alum.mit.edu>
Date:   Wed Apr 9 17:48:32 2014 -0700

    Avoid bug 9962 - don't use variables that haven't been set.

    See the comment for details.

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


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

GLib (gthread-posix.c): Unexpected error from C library during 'malloc': Cannot
allocate memory.  Aborting.

[ no debug trace ]


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