Wireshark-bugs: [Wireshark-bugs] [Bug 10098] New: Buildbot crash output: fuzz-2014-05-10-20877.p
| Bug ID |
10098
|
| Summary |
Buildbot crash output: fuzz-2014-05-10-20877.pcap
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
http://www.wireshark.org/download/automated/captures/fuzz-2014-05-10-20877.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-10-20877.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=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=2750
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=e5cfd9e13a0b6372b87727167843fa61d4926f95
Return value: 152
Dissector bug: 0
Valgrind error count: 0
Git commit
commit e5cfd9e13a0b6372b87727167843fa61d4926f95
Author: Guy Harris <guy@alum.mit.edu>
Date: Fri May 9 00:50:51 2014 -0700
Squelch compiler warnings.
Some are legitimate warnings - get_node_field_value() now returns a
value that the callers are expected to g_free(), so we'd better not
return a string constant.
Change-Id: I937254316119044691c1d9a3da8c9615763e2e5a
Reviewed-on: https://code.wireshark.org/review/1571
Reviewed-by: Guy Harris <guy@alum.mit.edu>
Command and args: ./tools/valgrind-wireshark.sh -T
==10533== Memcheck, a memory error detector
==10533== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==10533== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==10533== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-10-20877.pcap
==10533==
==10533==
==10533== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==10533== at 0xA59A03E: __write_nocancel (syscall-template.S:82)
==10533== by 0xA52C882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==10533== by 0xA52C749: new_do_write (fileops.c:543)
==10533== by 0xA52DEB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==10533== by 0xA52D024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==10533== by 0xA5225EC: fputs (iofputs.c:42)
==10533== by 0x65BE5C4: print_line_text (print.c:1157)
==10533== by 0x65C003A: print_hex_data_buffer (print.c:1049)
==10533== by 0x65C0116: print_hex_data (print.c:949)
==10533== by 0x41347D: print_packet (tshark.c:3962)
==10533== by 0x414472: process_packet (tshark.c:3551)
==10533== by 0x40BF82: main (tshark.c:3327)
==10533==
==10533== HEAP SUMMARY:
==10533== in use at exit: 26,485,870 bytes in 362,516 blocks
==10533== total heap usage: 39,762,285 allocs, 39,399,769 frees,
3,456,846,750 bytes allocated
==10533==
==10533== LEAK SUMMARY:
==10533== definitely lost: 304 bytes in 22 blocks
==10533== indirectly lost: 8 bytes in 1 blocks
==10533== possibly lost: 0 bytes in 0 blocks
==10533== still reachable: 26,485,558 bytes in 362,493 blocks
==10533== suppressed: 0 bytes in 0 blocks
==10533== Rerun with --leak-check=full to see details of leaked memory
==10533==
==10533== For counts of detected and suppressed errors, rerun with: -v
==10533== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 31 from 5)
./tools/valgrind-wireshark.sh: line 110: 10533 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.
