[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	12684
Summary	Buildbot crash output: fuzz-2016-07-28-19466.pcap
Product	Wireshark
Version	unspecified
Hardware	x86-64
URL	https://www.wireshark.org/download/automated/captures/fuzz-2016-07-28-19466.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-28-19466.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.cap

Build host information:
Linux wsbb04 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:26 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=13
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=8647f42d50b31e23091530a3c66895626e3a7dc4

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 8647f42d50b31e23091530a3c66895626e3a7dc4
Author: Guy Harris <guy@alum.mit.edu>
Date:   Wed Jul 27 14:31:21 2016 -0700

    If we don't get any OS information, remove the old OS information.

    The old information is copied over from one of the input files; if we
    don't have information about the OS on the machine writing the *output*
    file, just throw the old information away.

    (We need a better way to preserve information from the input files;
    perhaps this:

       http://www.winpcap.org/pipermail/pcap-ng-format/2016-June/000362.html

    might work.)

    Change-Id: Ia25771736d267173f2b6949a91e81e217ee7d16f
    Reviewed-on: https://code.wireshark.org/review/16730
    Reviewed-by: Guy Harris <guy@alum.mit.edu>
    (cherry picked from commit 93d5df468fc9013debe4a30f6f670eeedc01c911)
    Reviewed-on: https://code.wireshark.org/review/16731


==19519== Memcheck, a memory error detector
==19519== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==19519== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==19519== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-07-28-19466.pcap
==19519== 
==19519== 
==19519== HEAP SUMMARY:
==19519==     in use at exit: 1,511,588 bytes in 39,721 blocks
==19519==   total heap usage: 264,337 allocs, 224,616 frees, 30,409,624 bytes
allocated
==19519== 
==19519== LEAK SUMMARY:
==19519==    definitely lost: 332,918 bytes in 148 blocks
==19519==    indirectly lost: 725,414 bytes in 29,934 blocks
==19519==      possibly lost: 0 bytes in 0 blocks
==19519==    still reachable: 453,256 bytes in 9,639 blocks
==19519==         suppressed: 0 bytes in 0 blocks
==19519== Rerun with --leak-check=full to see details of leaked memory
==19519== 
==19519== For counts of detected and suppressed errors, rerun with: -v
==19519== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

[ no debug trace ]

---

      You are receiving this mail because:

• You are watching all bug changes.