Wireshark-bugs: [Wireshark-bugs] [Bug 7895] New: Buildbot crash output: fuzz-2012-10-22-13166.pc
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7895
Summary: Buildbot crash output: fuzz-2012-10-22-13166.pcap
Product: Wireshark
Version: unspecified
Platform: x86-64
URL: http://www.wireshark.org/download/automated/captures/f
uzz-2012-10-22-13166.pcap
OS/Version: Ubuntu
Status: NEW
Severity: Critical
Priority: High
Component: Dissection engine (libwireshark)
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: buildbot-do-not-reply@xxxxxxxxxxxxx
Build Information:
--
Problems have been found with the following capture file:
http://www.wireshark.org/download/automated/captures/fuzz-2012-10-22-13166.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 5071e32079f606efd667042f9e04fb3a0b890fb5
Author: Guy Harris <guy@xxxxxxxxxxxx>
Date: Mon Oct 22 10:06:13 2012 +0000
Pull the length-and-caplen setting operations in the read routines into
the macros.
Note why we don't pull the time setting operations into the macros (it's
because that would mean the macros can't be used in the seek-read
routines, as calculating time stamps requires accumulating the time
stamps in a sequential pass through the packets, given that the records
have time stamps relative to the previous packet).
Fix what is probably a typo in the definitions of some macros (which
happen to work without the fix because "fp" and "pp" are both local
variable names as well as macro arguments).
svn path=/trunk/; revision=45705
[ no debug trace ]
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
