Wireshark-bugs: [Wireshark-bugs] [Bug 10550] New: Buildbot crash output: fuzz-2014-10-09-5536.pc
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 09 Oct 2014 04:10:04 +0000
Bug ID 10550
Summary Buildbot crash output: fuzz-2014-10-09-5536.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2014-10-09-5536.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:

https://www.wireshark.org/download/automated/captures/fuzz-2014-10-09-5536.pcap

stderr:
Input file:
/home/wireshark/menagerie/menagerie/ITC_GTPU_eqm03s13p2-20120406-162430.pcap

Build host information:
Linux wsbb04 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=2990
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=e7e2f9c6397898b3a1000ac60412703423360790

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit e7e2f9c6397898b3a1000ac60412703423360790
Author: Guy Harris <guy@alum.mit.edu>
Date:   Wed Oct 8 17:27:08 2014 -0700

    Make the OPEN_INFO_ values members of an enum.

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


Command and args:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-nVxr


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

[ no debug trace ]

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