Wireshark-bugs: [Wireshark-bugs] [Bug 9984] New: Buildbot crash output: fuzz-2014-04-11-8332.pca
| Bug ID |
9984
|
| Summary |
Buildbot crash output: fuzz-2014-04-11-8332.pcap
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
http://www.wireshark.org/download/automated/captures/fuzz-2014-04-11-8332.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-2014-04-11-8332.pcap
stderr:
Input file:
/home/wireshark/menagerie/menagerie/10964-iDEN_UMTS_SIM_read.pcapng.gz
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://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=2693
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=2afa065d6201202c3804d8857c2f462e6dcde55f
Return value: 1
Dissector bug: 0
Valgrind error count: -1
Git commit
commit 2afa065d6201202c3804d8857c2f462e6dcde55f
Author: Stig Bjørlykke <stig@bjorlykke.org>
Date: Fri Apr 11 22:24:23 2014 +0200
Fix compilation if not HAVE_LIBGNUTLS and not HAVE_LIBGCRYPT
This was introduced in the previous compilation fix.
Change-Id: I4ec652a2708d90f35f3f00ec2c3261acb3e68397
Reviewed-on: https://code.wireshark.org/review/1074
Reviewed-by: Stig Bjørlykke <stig@bjorlykke.org>
Tested-by: Stig Bjørlykke <stig@bjorlykke.org>
Command and args: ./tools/valgrind-wireshark.sh
==6897== Memcheck, a memory error detector
==6897== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==6897== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==6897== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-04-11-8332.pcap
==6897==
==6897==
==6897== Valgrind's memory management: out of memory:
==6897== newSuperblock's request for 4194304 bytes failed.
==6897== 594391040 bytes have already been allocated.
==6897== Valgrind cannot continue. Sorry.
==6897==
==6897== There are several possible reasons for this.
==6897== - You have some kind of memory limit in place. Look at the
==6897== output of 'ulimit -a'. Is there a limit on the size of
==6897== virtual memory or address space?
==6897== - You have run out of swap space.
==6897== - Valgrind has a bug. If you think this is the case or you are
==6897== not sure, please let us know and we'll try to fix it.
==6897== Please note that programs can take substantially more memory than
==6897== normal when running under Valgrind tools, eg. up to twice or
==6897== more, depending on the tool. On a 64-bit machine, Valgrind
==6897== should be able to make use of up 32GB memory. On a 32-bit
==6897== machine, Valgrind should be able to use all the memory available
==6897== to a single process, up to 4GB if that's how you have your
==6897== kernel configured. Most 32-bit Linux setups allow a maximum of
==6897== 3GB per process.
==6897==
==6897== Whatever the reason, Valgrind cannot continue. Sorry.
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.
