| Bug ID |
10504
|
| Summary |
Buildbot crash output: fuzz-2014-09-25-22629.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2014-09-25-22629.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-25-22629.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/13092-dsr-3nodecapture.pcap.gz
Build host information:
Linux wsbb04 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 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=2977
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=e520b2b80002de80cf28e62abb537873d2abd259
Return value: 152
Dissector bug: 0
Valgrind error count: 0
Git commit
commit e520b2b80002de80cf28e62abb537873d2abd259
Author: Pascal Quantin <[email protected]>
Date: Thu Sep 25 15:21:11 2014 +0200
ANSI IS-637-A: fix dissection of fragmented Unicode SMS
The computation of the number of characters available was wrong when the
User Data Header is present
Change-Id: I2809c1460316530654a997b26cfc33c60a32fd6f
Reviewed-on: https://code.wireshark.org/review/4284
Petri-Dish: Pascal Quantin <[email protected]>
Tested-by: Petri Dish Buildbot <[email protected]>
Reviewed-by: Pascal Quantin <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh -T
==29850== Memcheck, a memory error detector
==29850== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==29850== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright
info
==29850== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-09-25-22629.pcap
==29850==
==29850==
==29850== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==29850== at 0xA78F3AE: __write_nocancel (syscall-template.S:81)
==29850== by 0xA71CA82: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1261)
==29850== by 0xA71DF5B: _IO_do_write@@GLIBC_2.2.5 (fileops.c:538)
==29850== by 0xA71D120: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1332)
==29850== by 0xA712243: fputs (iofputs.c:40)
==29850== by 0x66722E5: print_line_text (print.c:1150)
==29850== by 0x6673D57: print_hex_data_buffer (print.c:1042)
==29850== by 0x6674146: print_hex_data (print.c:942)
==29850== by 0x412B82: print_packet (tshark.c:3984)
==29850== by 0x413562: process_packet (tshark.c:3573)
==29850== by 0x40C4EE: main (tshark.c:3348)
==29850==
==29850== HEAP SUMMARY:
==29850== in use at exit: 30,654,753 bytes in 348,935 blocks
==29850== total heap usage: 80,535,647 allocs, 80,186,712 frees,
5,860,449,350 bytes allocated
==29850==
==29850== LEAK SUMMARY:
==29850== definitely lost: 304 bytes in 22 blocks
==29850== indirectly lost: 8 bytes in 1 blocks
==29850== possibly lost: 0 bytes in 0 blocks
==29850== still reachable: 30,654,441 bytes in 348,912 blocks
==29850== suppressed: 0 bytes in 0 blocks
==29850== Rerun with --leak-check=full to see details of leaked memory
==29850==
==29850== For counts of detected and suppressed errors, rerun with: -v
==29850== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
./tools/valgrind-wireshark.sh: line 113: 29850 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.
