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

stderr:
Input file: /home/wireshark/menagerie/menagerie/ndsp_v2.pcapng.gz

Build host information:
Linux wsbb04 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.3 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=3477
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=099698445b5cd60b00777ae47f68fba620fa975e

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 099698445b5cd60b00777ae47f68fba620fa975e
Author: Guy Harris <guy@alum.mit.edu>
Date:   Sun Jan 24 17:10:20 2016 -0800

    Move the proto data stuff out of frame_data.[ch].

    It's not tied to the frame_data structure any more, so it belongs by
    itself.

    Clean up some #includes while we're at it; in particular, frame_data.h
    doesn't use anything related to tvbuffs, so don't have it gratuitiously
    include tvbuff.h.

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


Command and args: ./tools/valgrind-wireshark.sh 

==7088== Memcheck, a memory error detector
==7088== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==7088== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==7088== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2016-01-26-17387.pcap
==7088== 
==7088== 
==7088== HEAP SUMMARY:
==7088==     in use at exit: 1,117,944 bytes in 32,494 blocks
==7088==   total heap usage: 591,944 allocs, 559,450 frees, 45,685,229 bytes
allocated
==7088== 
==7088== LEAK SUMMARY:
==7088==    definitely lost: 64,052 bytes in 3,939 blocks
==7088==    indirectly lost: 38,888 bytes in 139 blocks
==7088==      possibly lost: 0 bytes in 0 blocks
==7088==    still reachable: 1,015,004 bytes in 28,416 blocks
==7088==         suppressed: 0 bytes in 0 blocks
==7088== Rerun with --leak-check=full to see details of leaked memory
==7088== 
==7088== For counts of detected and suppressed errors, rerun with: -v
==7088== 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.