Wireshark-bugs: [Wireshark-bugs] [Bug 12578] New: Buildbot crash output: fuzz-2016-07-02-25220.p

Date: Sat, 02 Jul 2016 10:40:05 +0000
Bug ID 12578
Summary Buildbot crash output: fuzz-2016-07-02-25220.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-07-02-25220.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:

https://www.wireshark.org/download/automated/captures/fuzz-2016-07-02-25220.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/14695-sample.pcap

Build host information:
Linux wsbb04 3.13.0-86-generic #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_BUILDNUMBER=954
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-1.12/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=d49fb83f6f6b6ef4ffc4accb6c5071cca1f7b4be

Return value:  139

Dissector bug:  0

Valgrind error count:  0



Git commit
commit d49fb83f6f6b6ef4ffc4accb6c5071cca1f7b4be
Author: Ashish Shukla <[email protected]>
Date:   Fri Jun 24 15:59:39 2016 -0700

    radiotap: Fix for the VHT 20MHz MCS 9 data rate not displayed

    MCS 9 at 20 MHz is valid for 3 and 6 spatial streams.
    Changed the rate table to include rate (mbps) for VHT 20MHz MCS 9.

    Signed-off-by: Alexis La Goutte <[email protected]>

    Bug: 12558
    Change-Id: Ia16ae545a5ac1779131e24e1f54a5659390cd321
    Reviewed-on: https://code.wireshark.org/review/16146
    Reviewed-by: Guy Harris <[email protected]>
    (cherry picked from commit a4711f80c6d466cdd7eef376bf911699f55d35eb)
    Reviewed-on: https://code.wireshark.org/review/16161


Command and args:
/home/wireshark/builders/wireshark-1.12-fuzz/fuzztest/install/bin/tshark -nVxr


[ no debug trace ]


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