Wireshark-bugs: [Wireshark-bugs] [Bug 9959] New: Buildbot crash output: fuzz-2014-04-06-2679.pca

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 07 Apr 2014 11:00:03 +0000
Bug ID 9959
Summary Buildbot crash output: fuzz-2014-04-06-2679.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-06-2679.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-2014-04-06-2679.pcap

stderr:
Input file:
/home/wireshark/menagerie/menagerie/10648-dcp_split_00004_20130424095731

Build host information:
Linux wsbb04 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 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=
BUILDBOT_BUILDNUMBER=413
BUILDBOT_URL=http://buildbot.wireshark.org/trunk-1.10/
BUILDBOT_BUILDERNAME=Fuzz-Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=f91d6a2f8abc26997c6465c44d1eda97860c0ecb

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit f91d6a2f8abc26997c6465c44d1eda97860c0ecb
Author: Gerald Combs <[email protected]>
Date:   Sun Apr 6 08:09:33 2014 -0700

    [Automatic manuf, services and enterprise-numbers update for 2014-04-06]

    Change-Id: I16ed704d16c957e52a36af79edff626d4a9d67c0
    Reviewed-on: https://code.wireshark.org/review/980
    Reviewed-by: Alexis La Goutte <[email protected]>


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.