Wireshark-bugs: [Wireshark-bugs] [Bug 9228] New: Buildbot crash output: fuzz-2013-10-03-32239.pc
| Bug ID |
9228
|
| Summary |
Buildbot crash output: fuzz-2013-10-03-32239.pcap
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
http://www.wireshark.org/download/automated/captures/fuzz-2013-10-03-32239.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-10-03-32239.pcap
stderr:
Input file:
/home/wireshark/menagerie/menagerie/11687-sip_deflate_msg_body.pcapng
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=2117
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang-Code-Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=76c769e50b024f568c6051a6d699ed65a71df629
Return value: 134
Dissector bug: 0
Valgrind error count: 0
Git commit
commit 76c769e50b024f568c6051a6d699ed65a71df629
Author: Evan Huus <eapache@gmail.com>
Date: Fri Oct 4 02:21:39 2013 +0000
Initialize the SegmentType to the appropriate "Unknown" value so that if
the
subdissector bails early we don't use uninitialized memory. Also add
modelines.
Fixes https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9226
svn path=/trunk/; revision=52349
Command and args: ./tshark -nVxr
** (process:29119): WARNING **: Dissector bug, protocol SIP, in packet 1:
proto.c:3385: failed assertion "tvb != ((void *)0) || *length == 0"
Unhandled exception ("tvbuff.c:415: failed assertion "tvb &&
tvb->initialized"", group=1, code=5)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.
