Wireshark-bugs: [Wireshark-bugs] [Bug 8655] New: Buildbot crash output: fuzz-2013-05-13-20059.pc
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 13 May 2013 22:20:05 +0000
Bug ID 8655
Summary Buildbot crash output: fuzz-2013-05-13-20059.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2013-05-13-20059.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-05-13-20059.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/10749-test.pcapng.gz

Build host information:
Linux wsbb04 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 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=1896
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang-Code-Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=8ad81a426fb0abe1885f17d795f9ebb3a9c8c342

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 8ad81a426fb0abe1885f17d795f9ebb3a9c8c342
Author: Alexis La Goutte <alexis.lagoutte@gmail.com>
Date:   Mon May 13 20:24:22 2013 +0000

    Add wmem_test to .git(bzr)ignore

    svn path=/trunk/; revision=49275


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.