Wireshark-bugs: [Wireshark-bugs] [Bug 10103] New: Buildbot crash output: fuzz-2014-05-12-10771.p
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 13 May 2014 11:00:06 +0000
Bug ID 10103
Summary Buildbot crash output: fuzz-2014-05-12-10771.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-05-12-10771.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-12-10771.pcap

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

Build host information:
Linux wsbb04 3.2.0-61-generic #92-Ubuntu SMP Mon Mar 31 23:47:59 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=
BUILDBOT_BUILDNUMBER=2753
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=98f608cc0ddd5493a18e87ffe09ed551969b8ae3

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 98f608cc0ddd5493a18e87ffe09ed551969b8ae3
Author: Pascal Quantin <pascal.quantin@gmail.com>
Date:   Sun May 11 15:07:25 2014 +0200

    Identify client/server by their IP address and port number in follow
streams dialog box

    This allows to properly identify hosts that use the same port number

    Change-Id: I93bf5b53e4df1d339fb06b372b90f88fce6785a0
    Reviewed-on: https://code.wireshark.org/review/1588
    Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com>


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

==13779== Memcheck, a memory error detector
==13779== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==13779== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==13779== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-12-10771.pcap
==13779== 
==13779== 
==13779== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==13779==    at 0xA5A003E: __write_nocancel (syscall-template.S:82)
==13779==    by 0xA532882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==13779==    by 0xA532749: new_do_write (fileops.c:543)
==13779==    by 0xA533EB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==13779==    by 0xA533024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==13779==    by 0xA5285EC: fputs (iofputs.c:42)
==13779==    by 0x65C0944: print_line_text (print.c:1159)
==13779==    by 0x65C25F2: proto_tree_print_node (print.c:192)
==13779==    by 0x65C414B: proto_tree_children_foreach (proto.c:629)
==13779==    by 0x65C26BD: proto_tree_print_node (print.c:241)
==13779==    by 0x65C414B: proto_tree_children_foreach (proto.c:629)
==13779==    by 0x65C1785: proto_tree_print (print.c:153)
==13779== 
==13779== HEAP SUMMARY:
==13779==     in use at exit: 26,449,790 bytes in 360,135 blocks
==13779==   total heap usage: 40,155,334 allocs, 39,795,199 frees,
3,490,052,458 bytes allocated
==13779== 
==13779== LEAK SUMMARY:
==13779==    definitely lost: 304 bytes in 22 blocks
==13779==    indirectly lost: 8 bytes in 1 blocks
==13779==      possibly lost: 0 bytes in 0 blocks
==13779==    still reachable: 26,449,478 bytes in 360,112 blocks
==13779==         suppressed: 0 bytes in 0 blocks
==13779== Rerun with --leak-check=full to see details of leaked memory
==13779== 
==13779== For counts of detected and suppressed errors, rerun with: -v
==13779== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 55 from 5)
./tools/valgrind-wireshark.sh: line 113: 13779 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.