Wireshark-bugs: [Wireshark-bugs] [Bug 8539] New: Buildbot crash output: fuzz-2013-03-28-8509.pca
Date: Fri, 29 Mar 2013 10:30:04 +0000
Bug ID 8539
Summary Buildbot crash output: fuzz-2013-03-28-8509.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2013-03-28-8509.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-2013-03-28-8509.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/3989-fuzztest.pcap

Build host information:
Linux wsbb04 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 12.04.2 LTS
Release:    12.04
Codename:    precise

Buildbot information:
BUILDBOT_REPOSITORY=http://code.wireshark.org/git/wireshark
BUILDBOT_BUILDNUMBER=1855
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang-Code-Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=6f19d87f4e3aaa5872bdec1d9f4e50d85eee193d

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 6f19d87f4e3aaa5872bdec1d9f4e50d85eee193d
Author: Evan Huus <eapache@gmail.com>
Date:   Thu Mar 28 22:02:04 2013 +0000

    Greatly clean up value_string.c
     - use consistent indentation and coding style
     - add modelines
     - replace some g_assert calls with DISSECTOR_ASSERT where it makes sense
     - group related functions together and simplify many comments by referring
to
       the 'normal' value_string as the canonical version

    svn path=/trunk/; revision=48633


Command and args: ./tshark -nVxr


***MEMORY-ERROR***: [6340]: GSlice: failed to allocate 2032 bytes (alignment:
2048): Cannot allocate memory


[ no debug trace ]


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