Wireshark-bugs: [Wireshark-bugs] [Bug 12998] New: Buildbot crash output: fuzz-2016-10-10-22152.p
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 10 Oct 2016 19:10:03 +0000
Bug ID 12998
Summary Buildbot crash output: fuzz-2016-10-10-22152.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-10-10-22152.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-10-10-22152.pcap

stderr:
Input file:
/home/wireshark/menagerie/menagerie/12074-FR_to_T1_to_Enet_11nov.pcap

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=3739
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=9c2052796788cad58d1d356c1f230630a92b12a4

Return value:  0

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 9c2052796788cad58d1d356c1f230630a92b12a4
Author: Gerald Combs <gerald@wireshark.org>
Date:   Mon Oct 10 10:36:24 2016 -0700

    fuzz-test: Fix an exit status check.

    Make sure we check the exit status of the Valgrind process, not the most
    recently executed command.

    Change-Id: I3b6bd427383e4271b9ed38a10da6db506a511dc1
    Reviewed-on: https://code.wireshark.org/review/18138
    Reviewed-by: Gerald Combs <gerald@wireshark.org>



** (process:8902): 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.