Wireshark-bugs: [Wireshark-bugs] [Bug 12967] New: Buildbot crash output: fuzz-2016-09-29-12209.p
Date: Thu, 29 Sep 2016 20:40:03 +0000
Bug ID 12967
Summary Buildbot crash output: fuzz-2016-09-29-12209.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-09-29-12209.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-09-29-12209.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/14877-hart-ip.pcapng

Build host information:
Linux wsbb04 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:    16.04
Codename:    xenial

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=3710
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=e91af83c637adaa7a9837de65f50596a32b08db0

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit e91af83c637adaa7a9837de65f50596a32b08db0
Author: Guy Harris <guy@alum.mit.edu>
Date:   Wed Sep 28 21:35:12 2016 -0700

    Replace some seeks forward with wtap_read_bytes() with a null buffer
pointer.

    If the seek forward is just skipping record content that's not
    (currently) interesting, use wtap_read_bytes() with a null buffer
    pointer; it catches short "reads" and requires less seeking, so it may
    work better when reading from a pipe.

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



[ no debug trace ]


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