Wireshark-bugs: [Wireshark-bugs] [Bug 8285] New: Buildbot crash output: fuzz-2013-01-31-4808.pca
Date: Fri, 01 Feb 2013 01:40:02 +0000
Bug ID 8285
Summary Buildbot crash output: fuzz-2013-01-31-4808.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2013-01-31-4808.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-01-31-4808.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/8796-allCommands-01.cap

Build host information:
Linux wsbb04 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 12.04.1 LTS
Release:    12.04
Codename:    precise

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

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 7fb4d231c3fa80edfcce9944a90652ec274e24be
Author: Jeff Morriss <jeff.morriss.ws@gmail.com>
Date:   Thu Jan 31 22:43:04 2013 +0000

    Eliminate a bunch of basically useless/duplicate hf's for affected PCs:
they
    all have the same name and abbreviation so there's not much point in having
    multiple variables for them.  (Arguably the ansi_apc and chinese_apc
variables
    should be merged too but we may as well preserve the user interface: they
have
    different abbreviations.)

    (Prompted by Bill's discovery of a cut-n-paste problem which rendered a
couple
    of these hf's unused.)

    svn path=/trunk/; revision=47402


Command and args: ./tshark -nr

Out Of Memory!

Sorry, but TShark has to terminate now!

Some infos / workarounds can be found at:
http://wiki.wireshark.org/KnownBugs/OutOfMemory
Unhandled exception (group=1, code=6)

[ no debug trace ]


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