Wireshark-bugs: [Wireshark-bugs] [Bug 10134] New: Buildbot crash output: fuzz-2014-05-25-28169.p
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 25 May 2014 21:20:03 +0000
Bug ID 10134
Summary Buildbot crash output: fuzz-2014-05-25-28169.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-05-25-28169.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-05-25-28169.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/5472-tight-hex.pcap

Build host information:
Linux wsbb04 3.2.0-61-generic #93-Ubuntu SMP Fri May 2 21:31:50 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=2772
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=f8d63516351e67432e8bbeee4f1c2e57dbe11d0f

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit f8d63516351e67432e8bbeee4f1c2e57dbe11d0f
Author: Bill Meier <wmeier@newsguy.com>
Date:   Sun May 25 14:21:38 2014 -0400

    Fix [-Werror=clobbered] gcc warning

    Change-Id: Ibeef517a5100ae6d2c01f329022281b81a8b56a9
    Reviewed-on: https://code.wireshark.org/review/1795
    Reviewed-by: Bill Meier <wmeier@newsguy.com>


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


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

[ no debug trace ]

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