Wireshark-bugs: [Wireshark-bugs] [Bug 10117] New: Buildbot crash output: fuzz-2014-05-18-2001.pc
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 18 May 2014 21:40:05 +0000
Bug ID 10117
Summary Buildbot crash output: fuzz-2014-05-18-2001.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-05-18-2001.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-05-18-2001.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/1598-ws_00445_20080327094342.gz

Build host information:
Linux wsbb04 3.2.0-61-generic #93-Ubuntu SMP Fri May 2 21:31:50 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=2762
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=ba3c0d7c4d5fa71413587cbe62e555f5f4545fdd

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit ba3c0d7c4d5fa71413587cbe62e555f5f4545fdd
Author: Martin Mathieson <martin.r.mathieson@googlemail.com>
Date:   Fri May 16 17:19:17 2014 +0100

    Show EMM and ESM causes in the Info column

    Change-Id: I2e3be18e997d6be0b250fbd8e664779d0d2a8228
    Reviewed-on: https://code.wireshark.org/review/1666
    Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com>
    Reviewed-by: Evan Huus <eapache@gmail.com>


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

==22008== Memcheck, a memory error detector
==22008== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==22008== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==22008== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-18-2001.pcap
==22008== 
==22008== 
==22008== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==22008==    at 0x65C4E1B: proto_tree_add_node (proto.c:3765)
==22008==    by 0x65CCEFB: proto_tree_new_item (proto.c:1870)
==22008==    by 0x65CDC05: proto_tree_add_item_new (proto.c:1957)
==22008==    by 0x6BFA24A: dissect_sctp_chunk (packet-sctp.c:4113)
==22008==    by 0x6BFC346: dissect_sctp_packet (packet-sctp.c:4296)
==22008==    by 0x6BFCE41: dissect_sctp (packet-sctp.c:4513)
==22008==    by 0x65B66C7: call_dissector_through_handle (packet.c:596)
==22008==    by 0x65B71FD: call_dissector_work (packet.c:683)
==22008==    by 0x65B7A22: dissector_try_uint_new (packet.c:1114)
==22008==    by 0x6971C19: dissect_ip (packet-ip.c:2399)
==22008==    by 0x65B66C7: call_dissector_through_handle (packet.c:596)
==22008==    by 0x65B71FD: call_dissector_work (packet.c:683)
==22008== 
==22008== HEAP SUMMARY:
==22008==     in use at exit: 30,158,859 bytes in 419,965 blocks
==22008==   total heap usage: 54,344,735 allocs, 53,924,770 frees,
3,760,212,403 bytes allocated
==22008== 
==22008== LEAK SUMMARY:
==22008==    definitely lost: 304 bytes in 22 blocks
==22008==    indirectly lost: 8 bytes in 1 blocks
==22008==      possibly lost: 0 bytes in 0 blocks
==22008==    still reachable: 30,158,547 bytes in 419,942 blocks
==22008==         suppressed: 0 bytes in 0 blocks
==22008== Rerun with --leak-check=full to see details of leaked memory
==22008== 
==22008== For counts of detected and suppressed errors, rerun with: -v
==22008== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 83 from 5)
./tools/valgrind-wireshark.sh: line 113: 22008 CPU time limit exceeded (core
dumped) $LIBTOOL valgrind --suppressions=`dirname $0`/vg-suppressions
--tool=$TOOL $CALLGRIND_OUT_FILE $VERBOSE $LEAK_CHECK $REACHABLE $TRACK_ORIGINS
$COMMAND $COMMAND_ARGS $PCAP $COMMAND_ARGS2 > /dev/null

[ no debug trace ]

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