Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 7793] New: Buildbot crash output: fuzz-2012-10-03-9770.pcap

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7793

           Summary: Buildbot crash output: fuzz-2012-10-03-9770.pcap
           Product: Wireshark
           Version: unspecified
          Platform: x86-64
               URL: http://www.wireshark.org/download/automated/captures/f
                    uzz-2012-10-03-9770.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-03-9770.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 1fb353e77b30c8a83912b2485fca8cff143beaab
Author: Guy Harris <guy@xxxxxxxxxxxx>
Date:   Thu Oct 4 02:53:15 2012 +0000

    For VS 2005, also mention the IA-64 vcredist the first time we mention
    the versions of vcredist, just in case anybody is building for Itanium.
    The second time we mention them, mention all three, not just the 32-bit
    x86 version.  Rewrite the sentence for that a bit - it's not as if MSVC
    uses particular deployment methods, those were chosen by the Wireshark
    development team.

    For VS 2008, note that Microsoft mentions all three redistribution
    mechanisms, and link to the "Choosing a Deployment Method" page for VS
    2008 (which looks as if Microsoft didn't do a good job of editing it
    after copying-and-pasting the 2005 version, or didn't set up ASP or
    whatever it is that supplies VS-specific versions of the pages
    correctly).

    For VS 2010, note that Microsoft mentions all three redistribution
    mechanisms, link to the "Choosing a Deployment Method" page for VS 2010,
    and note that it recommends the method we chose and gives it as as the
    first method.

    svn path=/trunk/; revision=45302

[ 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.