Wireshark-bugs: [Wireshark-bugs] [Bug 8996] New: Buildbot crash output: fuzz-2013-07-31-14987.pc
Bug ID |
8996
|
Summary |
Buildbot crash output: fuzz-2013-07-31-14987.pcap
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
URL |
http://www.wireshark.org/download/automated/captures/fuzz-2013-07-31-14987.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-2013-07-31-14987.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/003transf.cap
Build host information:
Linux wsbb04 3.2.0-49-generic #75-Ubuntu SMP Tue Jun 18 17:39:32 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_BUILDNUMBER=2049
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang-Code-Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=559305882501d969884130c8cc8264aa70140595
Return value: 134
Dissector bug: 0
Valgrind error count: 0
Git commit
commit 559305882501d969884130c8cc8264aa70140595
Author: Guy Harris <guy@alum.mit.edu>
Date: Wed Jul 31 07:17:45 2013 +0000
If you use --enable-osx-deploy-target or --disable-osx-deploy-target on
anything other than OS X, fail; whatever it is you're trying to do won't
work (unless and until there exists a platform that fully supports
cross-development for OS X, *including* building against SDKs and
building with -mmacosx-version-min).
If you use neither on OS X, default to the OS major version on which
you're building. If you use --disable-osx-deploy-target, don't build
against an SDK and don't use -mmacosx-version-min.
svn path=/trunk/; revision=51057
Command and args: ./tshark -nVxr
**
ERROR:wmem_core.c:45:wmem_alloc: assertion failed: (allocator->in_scope)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.