Wireshark-bugs: [Wireshark-bugs] [Bug 9998] New: Buildbot crash output: fuzz-2014-04-16-11864.pc
Date: Wed, 16 Apr 2014 21:50:04 +0000
Bug ID 9998
Summary Buildbot crash output: fuzz-2014-04-16-11864.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-16-11864.pcap
OS Ubuntu
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Problems have been found with the following capture file:


Input file:

Build host information:
Linux wsbb04 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 12.04.4 LTS
Release:    12.04
Codename:    precise

Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark

Return value:  1

Dissector bug:  0

Valgrind error count:  -1

Git commit
commit 16b26b8e5fa066bfde0939ca2a66af00af44285e
Author: Guy Harris <[email protected]>
Date:   Mon Apr 14 15:43:03 2014 -0700

    Put the system ID in the top-level items for neighbors.

    Add a tvb_print_system_id() routine, and use that in various ISIS
    dissectors, while we're at it.

    Change-Id: I31b6b9ea8faf2b4849f974ec7ed27fbdd14b91ef
    Reviewed-on: https://code.wireshark.org/review/1145
    Reviewed-by: Guy Harris <[email protected]>

Command and args: ./tools/valgrind-wireshark.sh 

==19175== Memcheck, a memory error detector
==19175== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==19175== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==19175== Command:
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-04-16-11864.pcap
==19175==     Valgrind's memory management: out of memory:
==19175==        newSuperblock's request for 4194304 bytes failed.
==19175==        594587648 bytes have already been allocated.
==19175==     Valgrind cannot continue.  Sorry.
==19175==     There are several possible reasons for this.
==19175==     - You have some kind of memory limit in place.  Look at the
==19175==       output of 'ulimit -a'.  Is there a limit on the size of
==19175==       virtual memory or address space?
==19175==     - You have run out of swap space.
==19175==     - Valgrind has a bug.  If you think this is the case or you are
==19175==     not sure, please let us know and we'll try to fix it.
==19175==     Please note that programs can take substantially more memory than
==19175==     normal when running under Valgrind tools, eg. up to twice or
==19175==     more, depending on the tool.  On a 64-bit machine, Valgrind
==19175==     should be able to make use of up 32GB memory.  On a 32-bit
==19175==     machine, Valgrind should be able to use all the memory available
==19175==     to a single process, up to 4GB if that's how you have your
==19175==     kernel configured.  Most 32-bit Linux setups allow a maximum of
==19175==     3GB per process.
==19175==     Whatever the reason, Valgrind cannot continue.  Sorry.

[ no debug trace ]

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