Wireshark-bugs: [Wireshark-bugs] [Bug 9276] New: Buildbot crash output: fuzz-2013-10-16-32089.pc

Date: Wed, 16 Oct 2013 20:30:04 +0000
Bug ID 9276
Summary Buildbot crash output: fuzz-2013-10-16-32089.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2013-10-16-32089.pcap
OS Ubuntu
Status CONFIRMED
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Problems have been found with the following capture file:

http://www.wireshark.org/download/automated/captures/fuzz-2013-10-16-32089.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/10697-FirmwareDownload.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=http://code.wireshark.org/git/wireshark
BUILDBOT_BUILDNUMBER=2128
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang-Code-Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=09066e4ebaca66b7ab76565f556cd27c205c12dd

Return value:  133

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 09066e4ebaca66b7ab76565f556cd27c205c12dd
Author: Evan Huus <[email protected]>
Date:   Wed Oct 16 18:08:24 2013 +0000

    In packet-wsp.c, don't use the get_long_integer macro where we only need
the
    very smallest part of its logic. Just call tvb_get_guint8 directly and
check
    that the return is between 1 and 4. Properly fixes the set-but-unused and
    associated warnings that were showing up.

    svn path=/trunk/; revision=52648


Command and args: ./tshark -nVxr


** (process:24922): ERROR **: Memory corrupted

[ no debug trace ]


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