Wireshark-bugs: [Wireshark-bugs] [Bug 9257] New: Buildbot crash output: fuzz-2013-10-08-17329.pc

Date: Wed, 09 Oct 2013 17:30:03 +0000
Bug ID 9257
Summary Buildbot crash output: fuzz-2013-10-08-17329.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2013-10-08-17329.pcap
OS Ubuntu
Status CONFIRMED
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Problems have been found with the following capture file:

http://www.wireshark.org/download/automated/captures/fuzz-2013-10-08-17329.pcap

stderr:
Input file:
/home/wireshark/menagerie/menagerie/10649-dcp_split_00003_20130424095716

Build host information:
Linux wsbb04 3.2.0-49-generic #75-Ubuntu SMP Tue Jun 18 17:39:32 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=
BUILDBOT_BUILDNUMBER=226
BUILDBOT_URL=http://buildbot.wireshark.org/trunk-1.10/
BUILDBOT_BUILDERNAME=Fuzz-Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=e55355135253a2f7f171586d0ba27aa82c1c2965

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit e55355135253a2f7f171586d0ba27aa82c1c2965
Author: Evan Huus <[email protected]>
Date:   Mon Oct 7 23:38:07 2013 +0000

    The trunk fix for https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9232
is
    not easily backportable because wmem_strbuf is not fully implemented in
1.10.
    Instead, fix it by making sure that if our manual string-counter does
overflow
    past the end of the buffer, we reset it back.

    svn path=/trunk-1.10/; revision=52444


Command and args: ./tshark -nVxr

Out Of Memory!

Sorry, but TShark has to terminate now!

Some infos / workarounds can be found at:
http://wiki.wireshark.org/KnownBugs/OutOfMemory
**
ERROR:wmem_scopes.c:125:wmem_leave_file_scope: assertion failed:
(!in_packet_scope)

[ no debug trace ]


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