Wireshark-bugs: [Wireshark-bugs] [Bug 12600] New: Buildbot crash output: fuzz-2016-07-09-7629.pc
Date: Sat, 09 Jul 2016 15:40:03 +0000
Bug ID 12600
Summary Buildbot crash output: fuzz-2016-07-09-7629.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-07-09-7629.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:

https://www.wireshark.org/download/automated/captures/fuzz-2016-07-09-7629.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/14708-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=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=3615
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=01c6483b45a91f8c03eeb4bf80a15a5e174ffb18

Return value:  133

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 01c6483b45a91f8c03eeb4bf80a15a5e174ffb18
Author: Guy Harris <guy@alum.mit.edu>
Date:   Sat Jul 9 00:07:52 2016 -0700

    Check for pcapng files when reading from a pipe.

    That way, people don't get confused by an "Unrecognized libpcap format"
    error - it's *not* libpcap format!

    Also, improve *that* message to say "...or not libpcap data", and put a
    period at the end of the error messages.

    Change-Id: I175f9399fe99ce424f1d83596b7330e1fa5c0625
    Reviewed-on: https://code.wireshark.org/review/16349
    Reviewed-by: Guy Harris <guy@alum.mit.edu>



** (process:7538): ERROR **: More than 1000000 items in the tree -- possible
infinite loop

[ no debug trace ]


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