Wireshark-bugs: [Wireshark-bugs] [Bug 12599] New: Buildbot crash output: fuzz-2016-07-09-21216.p

Date: Sat, 09 Jul 2016 10:30:05 +0000
Bug ID 12599
Summary Buildbot crash output: fuzz-2016-07-09-21216.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-07-09-21216.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-09-21216.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=
BUILDBOT_BUILDNUMBER=961
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-1.12/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=432bae94f8faf795d59f994a31b9e79935cbf29f

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 432bae94f8faf795d59f994a31b9e79935cbf29f
Author: Guy Harris <[email protected]>
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 <[email protected]>
    Reviewed-on: https://code.wireshark.org/review/16353


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

GLib (gthread-posix.c): Unexpected error from C library during 'malloc': Cannot
allocate memory.  Aborting.

[ no debug trace ]


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