Wireshark-bugs: [Wireshark-bugs] [Bug 10711] New: Buildbot crash output: fuzz-2014-11-17-25060.p

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 17 Nov 2014 13:50:03 +0000
Bug ID 10711
Summary Buildbot crash output: fuzz-2014-11-17-25060.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2014-11-17-25060.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:

https://www.wireshark.org/download/automated/captures/fuzz-2014-11-17-25060.pcap

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

Build host information:
Linux wsbb04 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_BUILDNUMBER=624
BUILDBOT_URL=http://buildbot.wireshark.org/trunk-1.10/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=8061eaf12f03e444e92c96c97cce2f41a32a0844

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 8061eaf12f03e444e92c96c97cce2f41a32a0844
Author: Gerald Combs <[email protected]>
Date:   Sun Nov 16 08:15:39 2014 -0800

    [Automatic manuf, services and enterprise-numbers update for 2014-11-16]

    Change-Id: Icc4dbff45fb2461a27642121f463b820ce400984
    Reviewed-on: https://code.wireshark.org/review/5348
    Reviewed-by: Gerald Combs <[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.