Wireshark-bugs: [Wireshark-bugs] [Bug 10286] New: Buildbot crash output: fuzz-2014-07-15-23779.p
| Bug ID |
10286
|
| Summary |
Buildbot crash output: fuzz-2014-07-15-23779.pcap
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
http://www.wireshark.org/download/automated/captures/fuzz-2014-07-15-23779.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-07-15-23779.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/6656-ani_20110706172821.pcap
Build host information:
Linux wsbb04 3.2.0-65-generic #98-Ubuntu SMP Wed Jun 11 20:27:07 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=2857
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=e11db2ea032080f07e38acb00b2e4ea3a224b366
Return value: 152
Dissector bug: 0
Valgrind error count: 0
Git commit
commit e11db2ea032080f07e38acb00b2e4ea3a224b366
Author: Graham Bloice <graham.bloice@trihedral.com>
Date: Mon Jul 14 15:22:53 2014 +0100
Rename parameter if_index to stop clang warning:
capture_opts.c:1017:61: error: declaration of 'index' shadows a global
declaration [-Werror=shadow]
Change-Id: Ie409b4fa7abeb85e460bea398735cdc98d9034b1
Reviewed-on: https://code.wireshark.org/review/3041
Reviewed-by: Graham Bloice <graham.bloice@trihedral.com>
Command and args: ./tools/valgrind-wireshark.sh -T
==21551== Memcheck, a memory error detector
==21551== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==21551== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==21551== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-07-15-23779.pcap
==21551==
==21551==
==21551== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==21551== at 0xA65C03E: __write_nocancel (syscall-template.S:82)
==21551== by 0xA5EE882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==21551== by 0xA5EE749: new_do_write (fileops.c:543)
==21551== by 0xA5EFEB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==21551== by 0xA5EF024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==21551== by 0xA5E45EC: fputs (iofputs.c:42)
==21551== by 0x66180C4: print_line_text (print.c:1150)
==21551== by 0x6619DB2: proto_tree_print_node (print.c:192)
==21551== by 0x661B92B: proto_tree_children_foreach (proto.c:614)
==21551== by 0x6619E7D: proto_tree_print_node (print.c:241)
==21551== by 0x661B92B: proto_tree_children_foreach (proto.c:614)
==21551== by 0x6618F45: proto_tree_print (print.c:153)
==21551==
==21551== HEAP SUMMARY:
==21551== in use at exit: 59,902,366 bytes in 936,127 blocks
==21551== total heap usage: 53,669,923 allocs, 52,733,796 frees,
3,639,482,696 bytes allocated
==21551==
==21551== LEAK SUMMARY:
==21551== definitely lost: 289 bytes in 21 blocks
==21551== indirectly lost: 8 bytes in 1 blocks
==21551== possibly lost: 15 bytes in 1 blocks
==21551== still reachable: 59,902,054 bytes in 936,104 blocks
==21551== suppressed: 0 bytes in 0 blocks
==21551== Rerun with --leak-check=full to see details of leaked memory
==21551==
==21551== For counts of detected and suppressed errors, rerun with: -v
==21551== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 39 from 5)
./tools/valgrind-wireshark.sh: line 113: 21551 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.
