Wireshark-bugs: [Wireshark-bugs] [Bug 9974] New: Buildbot crash output: fuzz-2014-04-08-10101.pc
Date: Wed, 09 Apr 2014 20:31:08 +0000
Bug ID 9974
Summary Buildbot crash output: fuzz-2014-04-08-10101.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-08-10101.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:

http://www.wireshark.org/download/automated/captures/fuzz-2014-04-08-10101.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://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=2670
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=d3df2e588bc6febb5b2d414ad040ede903ef4c85

Return value:  139

Dissector bug:  0

Valgrind error count:  0



Git commit
commit d3df2e588bc6febb5b2d414ad040ede903ef4c85
Author: Guy Harris <guy@alum.mit.edu>
Date:   Tue Apr 8 01:22:57 2014 -0700

    On UN*X, <arpa/inet.h> suffices for struct in_addr and in_addr_t.

    So don't pull in <netinet/in.h>.  Also, avoid <sys/types.h> in
    packet-dcom.c.

    While we're at it, do *not* assume that pinfo->src or pinfo->dst are
    IPv4 addresses.

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


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


[ no debug trace ]


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