Wireshark-bugs: [Wireshark-bugs] [Bug 8028] New: Buildbot crash output: fuzz-2012-11-30-1917.pca
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 01 Dec 2012 19:52:53 +0000
Bug ID 8028
Summary Buildbot crash output: fuzz-2012-11-30-1917.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
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-2012-11-30-1917.pcap

stderr:
Command and args:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/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

Git commit
commit 3a0a1d49ea90c251450d2c9898311ed459bf9a32
Author: Jeff Morriss <jeff.morriss.ws@gmail.com>
Date:   Fri Nov 30 20:25:21 2012 +0000

    Fix an unitialized-read detected by Valgrind while processing:

   
https://www.wireshark.org/download/automated/captures/fuzz-2012-11-30-20336.pcap

    (I can't reproduce the actual fuzz failure and this uninitialized-read
    shouldn't have caused an out-of-memory condition--which is what the
buildbot
    said the problem with that capture was.)

    Also stop marking a variable that is used as unused.

    svn path=/trunk/; revision=46309

[ no debug trace ]

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