Wireshark-bugs: [Wireshark-bugs] [Bug 9966] New: Buildbot crash output: fuzz-2014-04-08-31804.pc

Date: Wed, 09 Apr 2014 20:30:29 +0000
Bug ID 9966
Summary Buildbot crash output: fuzz-2014-04-08-31804.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-08-31804.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-2014-04-08-31804.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/12657-lbtrm-uim-ump.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://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=2669
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=abbdcd875048e9182ea8f3674c0a452e64095125

Return value:  139

Dissector bug:  0

Valgrind error count:  0



Git commit
commit abbdcd875048e9182ea8f3674c0a452e64095125
Author: Alexis La Goutte <[email protected]>
Date:   Tue Apr 8 08:44:44 2014 +0200

    Fix warning found by -Wunused-const-variable (Clang 3.5)

    Change-Id: I4506be6ae8deda5e8d1e038b089620a15b650b03
    Reviewed-on: https://code.wireshark.org/review/1000
    Reviewed-by: Hadriel Kaplan <[email protected]>
    Reviewed-by: Anders Broman <[email protected]>


Command and args:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-nVxr


** (process:5162): WARNING **: Dissector bug, protocol LBMR, in packet 1082:
proto.c:4360: failed assertion "idx >= 0 && idx < num_tree_types"

[ no debug trace ]


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