Wireshark-bugs: [Wireshark-bugs] [Bug 10408] New: Buildbot crash output: fuzz-2014-08-23-12325.p

Date: Sun, 24 Aug 2014 22:10:07 +0000
Bug ID 10408
Summary Buildbot crash output: fuzz-2014-08-23-12325.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2014-08-23-12325.pcap
OS Ubuntu
Status CONFIRMED
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2014-08-23-12325.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/6656-ani_20110706172821.pcap

Build host information:
Linux wsbb04 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=2933
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=28acde13339f0dd59698a8dfeaf0430c61e00148

Return value:  152

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 28acde13339f0dd59698a8dfeaf0430c61e00148
Author: Marian Ďurkovič <[email protected]>
Date:   Wed Aug 20 11:30:44 2014 +0200

    Parse Capabilities & Flags section of TRILL Version Sub-TLV

    Change-Id: Ic82a2368c865031eaeee291055b6a4f176cde759
    Reviewed-on: https://code.wireshark.org/review/3792
    Reviewed-by: Anders Broman <[email protected]>


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

==22547== Memcheck, a memory error detector
==22547== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==22547== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright
info
==22547== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-08-23-12325.pcap
==22547== 
==22547== 
==22547== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==22547==    at 0xA71C6FE: __write_nocancel (syscall-template.S:81)
==22547==    by 0xA6A9E42: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1261)
==22547==    by 0xA6AB31B: _IO_do_write@@GLIBC_2.2.5 (fileops.c:538)
==22547==    by 0xA6AA4E0: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1332)
==22547==    by 0xA69F603: fputs (iofputs.c:40)
==22547==    by 0x664AC55: print_line_text (print.c:1150)
==22547==    by 0x664C6C7: print_hex_data_buffer (print.c:1042)
==22547==    by 0x664CAB6: print_hex_data (print.c:942)
==22547==    by 0x412B42: print_packet (tshark.c:3983)
==22547==    by 0x413522: process_packet (tshark.c:3572)
==22547==    by 0x40C4FE: main (tshark.c:3348)
==22547== 
==22547== HEAP SUMMARY:
==22547==     in use at exit: 63,773,879 bytes in 1,008,198 blocks
==22547==   total heap usage: 71,282,987 allocs, 70,274,789 frees,
4,776,252,109 bytes allocated
==22547== 
==22547== LEAK SUMMARY:
==22547==    definitely lost: 304 bytes in 22 blocks
==22547==    indirectly lost: 8 bytes in 1 blocks
==22547==      possibly lost: 0 bytes in 0 blocks
==22547==    still reachable: 63,773,567 bytes in 1,008,175 blocks
==22547==         suppressed: 0 bytes in 0 blocks
==22547== Rerun with --leak-check=full to see details of leaked memory
==22547== 
==22547== For counts of detected and suppressed errors, rerun with: -v
==22547== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
./tools/valgrind-wireshark.sh: line 113: 22547 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.