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

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit fe053839f07c3fb1a9fc3cd8e729f52b3823bcc4
Author: Alexis La Goutte <alexis.lagoutte@gmail.com>
Date:   Sun May 18 21:20:24 2014 +0200

    Fix Dead Store (Dead assignement/Dead increment) warning found by Clang

    Change-Id: I9bf53014d90857b7d71efbb09b5ceb708b3df6ca
    Reviewed-on: https://code.wireshark.org/review/1683
    Reviewed-by: Michael Mann <mmann78@netscape.net>


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

==3391== Memcheck, a memory error detector
==3391== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==3391== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==3391== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-20-5906.pcap
==3391== 
==3391== 
==3391== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==3391==    at 0xA5A103E: __write_nocancel (syscall-template.S:82)
==3391==    by 0xA533882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==3391==    by 0xA533749: new_do_write (fileops.c:543)
==3391==    by 0xA534EB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==3391==    by 0xA534024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==3391==    by 0xA529CDC: fwrite (iofwrite.c:45)
==3391==    by 0x65C15AD: print_line_text (print.c:1157)
==3391==    by 0x65C3282: proto_tree_print_node (print.c:192)
==3391==    by 0x65C4DDB: proto_tree_children_foreach (proto.c:629)
==3391==    by 0x65C334D: proto_tree_print_node (print.c:241)
==3391==    by 0x65C4DDB: proto_tree_children_foreach (proto.c:629)
==3391==    by 0x65C2415: proto_tree_print (print.c:153)
==3391== 
==3391== HEAP SUMMARY:
==3391==     in use at exit: 30,768,043 bytes in 422,134 blocks
==3391==   total heap usage: 54,347,996 allocs, 53,925,862 frees, 3,763,354,420
bytes allocated
==3391== 
==3391== LEAK SUMMARY:
==3391==    definitely lost: 304 bytes in 22 blocks
==3391==    indirectly lost: 8 bytes in 1 blocks
==3391==      possibly lost: 0 bytes in 0 blocks
==3391==    still reachable: 30,767,731 bytes in 422,111 blocks
==3391==         suppressed: 0 bytes in 0 blocks
==3391== Rerun with --leak-check=full to see details of leaked memory
==3391== 
==3391== For counts of detected and suppressed errors, rerun with: -v
==3391== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 75 from 5)
./tools/valgrind-wireshark.sh: line 113:  3391 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.