| Bug ID |
10441
|
| Summary |
Buildbot crash output: fuzz-2014-09-02-20036.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2014-09-02-20036.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-09-02-20036.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=2951
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=eb14a1f9323df051f4facadcf64fe729b1c42928
Return value: 152
Dissector bug: 0
Valgrind error count: 0
Git commit
commit eb14a1f9323df051f4facadcf64fe729b1c42928
Author: Gerald Combs <[email protected]>
Date: Sat Aug 30 18:02:52 2014 -0700
WSUG: Convert the ``File I/O'' chapter to AsciiDoc.
Leave most of the content intact for now. Remove images for
no-longer-supported versions of GTK+. Add an example for building the
Guides to README.cmake.
Change-Id: Id9e6a308c91b594d1fb7f107d7b9b28074a92a8b
Reviewed-on: https://code.wireshark.org/review/3931
Petri-Dish: Gerald Combs <[email protected]>
Tested-by: Petri Dish Buildbot <[email protected]>
Reviewed-by: Gerald Combs <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh -T
==22987== Memcheck, a memory error detector
==22987== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==22987== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright
info
==22987== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-09-02-20036.pcap
==22987==
==22987==
==22987== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==22987== at 0xA73A6FE: __write_nocancel (syscall-template.S:81)
==22987== by 0xA6C7E42: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1261)
==22987== by 0xA6C931B: _IO_do_write@@GLIBC_2.2.5 (fileops.c:538)
==22987== by 0xA6C84E0: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1332)
==22987== by 0xA6BD603: fputs (iofputs.c:40)
==22987== by 0x6655515: print_line_text (print.c:1150)
==22987== by 0x66570ED: proto_tree_print_node (print.c:192)
==22987== by 0x6658B8B: proto_tree_children_foreach (proto.c:615)
==22987== by 0x66571A6: proto_tree_print_node (print.c:241)
==22987== by 0x6658B8B: proto_tree_children_foreach (proto.c:615)
==22987== by 0x66571A6: proto_tree_print_node (print.c:241)
==22987== by 0x6658B8B: proto_tree_children_foreach (proto.c:615)
==22987==
==22987== HEAP SUMMARY:
==22987== in use at exit: 63,545,737 bytes in 1,020,522 blocks
==22987== total heap usage: 71,260,173 allocs, 70,239,651 frees,
4,777,845,735 bytes allocated
==22987==
==22987== LEAK SUMMARY:
==22987== definitely lost: 304 bytes in 22 blocks
==22987== indirectly lost: 8 bytes in 1 blocks
==22987== possibly lost: 0 bytes in 0 blocks
==22987== still reachable: 63,545,425 bytes in 1,020,499 blocks
==22987== suppressed: 0 bytes in 0 blocks
==22987== Rerun with --leak-check=full to see details of leaked memory
==22987==
==22987== For counts of detected and suppressed errors, rerun with: -v
==22987== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
./tools/valgrind-wireshark.sh: line 113: 22987 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.
