| Bug ID |
10131
|
| Summary |
Buildbot crash output: fuzz-2014-05-23-21602.pcap
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
http://www.wireshark.org/download/automated/captures/fuzz-2014-05-23-21602.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:
http://www.wireshark.org/download/automated/captures/fuzz-2014-05-23-21602.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/1598-ws_00445_20080327094342.gz
Build host information:
Linux wsbb04 3.2.0-61-generic #93-Ubuntu SMP Fri May 2 21:31:50 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://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=2765
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=adb3f70f920a2cf1c28da42f5482ce316a252de8
Return value: 152
Dissector bug: 0
Valgrind error count: 0
Git commit
commit adb3f70f920a2cf1c28da42f5482ce316a252de8
Author: Roman Volkov <[email protected]>
Date: Thu May 22 00:38:54 2014 +0300
Wrong length of Modulation Type and Modulation System fields in Satellite
Delivery Descriptor
According EN300468 in Satellite Delivery Descriptor 'Modulation System'
field has 1 bit length. 'Modulation Type' has 2 bits length.
But in my Wireshark 'Modulation System' is 2 bit long and 'Modulation Type'
is 1 bit long.
bug: 10119
Change-Id: I762145418bbfc9c0621ee7ca1a07d35afb6d7d92
Reviewed-on: https://code.wireshark.org/review/1718
Reviewed-by: Michael Mann <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh -T
==9145== Memcheck, a memory error detector
==9145== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==9145== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==9145== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-05-23-21602.pcap
==9145==
==9145==
==9145== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==9145== at 0xA5B003E: __write_nocancel (syscall-template.S:82)
==9145== by 0xA542882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289)
==9145== by 0xA542749: new_do_write (fileops.c:543)
==9145== by 0xA543EB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516)
==9145== by 0xA543024: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1371)
==9145== by 0xA538CDC: fwrite (iofwrite.c:45)
==9145== by 0x65C673D: print_line_text (print.c:1143)
==9145== by 0x65C83E2: proto_tree_print_node (print.c:192)
==9145== by 0x65C9F1B: proto_tree_children_foreach (proto.c:629)
==9145== by 0x65C84AD: proto_tree_print_node (print.c:241)
==9145== by 0x65C9F1B: proto_tree_children_foreach (proto.c:629)
==9145== by 0x65C84AD: proto_tree_print_node (print.c:241)
==9145==
==9145== HEAP SUMMARY:
==9145== in use at exit: 30,698,462 bytes in 421,928 blocks
==9145== total heap usage: 54,057,788 allocs, 53,635,860 frees, 3,743,878,679
bytes allocated
==9145==
==9145== LEAK SUMMARY:
==9145== definitely lost: 304 bytes in 22 blocks
==9145== indirectly lost: 8 bytes in 1 blocks
==9145== possibly lost: 0 bytes in 0 blocks
==9145== still reachable: 30,698,150 bytes in 421,905 blocks
==9145== suppressed: 0 bytes in 0 blocks
==9145== Rerun with --leak-check=full to see details of leaked memory
==9145==
==9145== For counts of detected and suppressed errors, rerun with: -v
==9145== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 71 from 5)
./tools/valgrind-wireshark.sh: line 113: 9145 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.
