Wireshark-bugs: [Wireshark-bugs] [Bug 10137] New: Buildbot crash output: fuzz-2014-05-27-2352.pc
Date: Tue, 27 May 2014 12:30:07 +0000
Bug ID 10137
Summary Buildbot crash output: fuzz-2014-05-27-2352.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-05-27-2352.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-27-2352.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=2773
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=37d40eb210b6192909dc27cd91592a796a7731cd

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 37d40eb210b6192909dc27cd91592a796a7731cd
Author: Pascal Quantin <pascal.quantin@gmail.com>
Date:   Sun May 25 23:13:57 2014 +0200

    MAC LTE: fix dissection of Extended Power Headroom control element

    Change-Id: Ia57b4769732f2e18dd2864b576c5c77fc68deb20
    Reviewed-on: https://code.wireshark.org/review/1798
    Reviewed-by: Pascal Quantin <pascal.quantin@gmail.com>


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

==32120== Memcheck, a memory error detector
==32120== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==32120== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==32120== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-27-2352.pcap
==32120== 
==32120== 
==32120== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==32120==    at 0xA54A713: _IO_str_init_static_internal (strops.c:55)
==32120==    by 0xA5D64B1: __vsnprintf_chk (vsnprintf_chk.c:64)
==32120==    by 0x98F3D91: g_snprintf (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.4)
==32120==    by 0x65D4C1C: proto_item_fill_label (proto.c:5837)
==32120==    by 0x65C950D: proto_tree_print_node (print.c:186)
==32120==    by 0x65CAE5B: proto_tree_children_foreach (proto.c:629)
==32120==    by 0x65C93ED: proto_tree_print_node (print.c:241)
==32120==    by 0x65CAE5B: proto_tree_children_foreach (proto.c:629)
==32120==    by 0x65C84B5: proto_tree_print (print.c:153)
==32120==    by 0x413480: print_packet (tshark.c:3939)
==32120==    by 0x4144D2: process_packet (tshark.c:3551)
==32120==    by 0x40BFC9: main (tshark.c:3327)
==32120== 
==32120== HEAP SUMMARY:
==32120==     in use at exit: 30,882,466 bytes in 425,385 blocks
==32120==   total heap usage: 55,213,481 allocs, 54,788,096 frees,
3,824,341,612 bytes allocated
==32120== 
==32120== LEAK SUMMARY:
==32120==    definitely lost: 304 bytes in 22 blocks
==32120==    indirectly lost: 8 bytes in 1 blocks
==32120==      possibly lost: 0 bytes in 0 blocks
==32120==    still reachable: 30,882,154 bytes in 425,362 blocks
==32120==         suppressed: 0 bytes in 0 blocks
==32120== Rerun with --leak-check=full to see details of leaked memory
==32120== 
==32120== For counts of detected and suppressed errors, rerun with: -v
==32120== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 61 from 5)
./tools/valgrind-wireshark.sh: line 113: 32120 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.