Wireshark-bugs: [Wireshark-bugs] [Bug 10163] New: Buildbot crash output: fuzz-2014-06-04-32203.p
Date: Thu, 05 Jun 2014 06:20:07 +0000
Bug ID 10163
Summary Buildbot crash output: fuzz-2014-06-04-32203.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-06-04-32203.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-06-04-32203.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=2785
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=3eacdda619bd9ec4f16863934415c3fc79f65e18

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 3eacdda619bd9ec4f16863934415c3fc79f65e18
Author: AndersBroman <anders.broman@ericsson.com>
Date:   Tue Jun 3 16:31:11 2014 +0200

    Change ep_alloc() to wmem_new() change depcrecated API.

    Change-Id: I1eb3d3f3ccdfa265099446e8d609273867304a73
    Reviewed-on: https://code.wireshark.org/review/1936
    Reviewed-by: Anders Broman <a.broman58@gmail.com>


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

==17641== Memcheck, a memory error detector
==17641== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==17641== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==17641== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-06-04-32203.pcap
==17641== 
==17641== 
==17641== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==17641==    at 0xA5D203E: __write_nocancel (syscall-template.S:82)
==17641==    by 0xA564882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==17641==    by 0xA564749: new_do_write (fileops.c:543)
==17641==    by 0xA565EB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==17641==    by 0xA565024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==17641==    by 0xA55A5EC: fputs (iofputs.c:42)
==17641==    by 0x65CACE4: print_line_text (print.c:1145)
==17641==    by 0x65CC962: proto_tree_print_node (print.c:192)
==17641==    by 0x65CE49B: proto_tree_children_foreach (proto.c:629)
==17641==    by 0x65CCA2D: proto_tree_print_node (print.c:241)
==17641==    by 0x65CE49B: proto_tree_children_foreach (proto.c:629)
==17641==    by 0x65CBAF5: proto_tree_print (print.c:153)
==17641== 
==17641== HEAP SUMMARY:
==17641==     in use at exit: 30,857,837 bytes in 424,968 blocks
==17641==   total heap usage: 54,854,308 allocs, 54,429,340 frees,
3,798,601,799 bytes allocated
==17641== 
==17641== LEAK SUMMARY:
==17641==    definitely lost: 304 bytes in 22 blocks
==17641==    indirectly lost: 8 bytes in 1 blocks
==17641==      possibly lost: 0 bytes in 0 blocks
==17641==    still reachable: 30,857,525 bytes in 424,945 blocks
==17641==         suppressed: 0 bytes in 0 blocks
==17641== Rerun with --leak-check=full to see details of leaked memory
==17641== 
==17641== For counts of detected and suppressed errors, rerun with: -v
==17641== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 65 from 5)
./tools/valgrind-wireshark.sh: line 113: 17641 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.