| Bug ID |
10724
|
| Summary |
Buildbot crash output: fuzz-2014-11-22-10244.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2014-11-22-10244.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-11-22-10244.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/file.dmp.gz
Build host information:
Linux wsbb04 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 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=3067
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=1cde31811793432cf4b9c307b51bc5d989925dd8
Return value: 0
Dissector bug: 0
Valgrind error count: 771
Git commit
commit 1cde31811793432cf4b9c307b51bc5d989925dd8
Author: Michał Orynicz <[email protected]>
Date: Thu Nov 20 13:16:33 2014 +0100
Fix for very big pid and tid numbers in logcat_text
There can be no space after pid colon if tid is big enough
in logcat long format.
Change-Id: I8e03e78c88e4bef1a5fdb3a04b77f58fa7d055bc
Reviewed-on: https://code.wireshark.org/review/5411
Reviewed-by: Michal Labedzki <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh
==31263== Memcheck, a memory error detector
==31263== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==31263== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright
info
==31263== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-11-22-10244.pcap
==31263==
==31263== Invalid read of size 1
==31263== at 0x9B081B4: g_strlcpy (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4002.0)
==31263== by 0x668C576: address_to_str_buf (address_to_str.c:604)
==31263== by 0x6690A84: col_set_addr.isra.5.part.6 (column-utils.c:1805)
==31263== by 0x6692FD2: col_fill_in (column-utils.c:2093)
==31263== by 0x412F05: print_packet (tshark.c:3892)
==31263== by 0x413A0A: process_packet (tshark.c:3541)
==31263== by 0x40C837: main (tshark.c:3315)
==31263== Address 0x11b11d60 is 0 bytes inside a block of size 80 free'd
==31263== at 0x4C2BDEC: free (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==31263== by 0x71CFE8C: wmem_simple_free_all (wmem_allocator_simple.c:107)
==31263== by 0x71D0B0B: wmem_leave_packet_scope (wmem_scopes.c:81)
==31263== by 0x4136C3: process_packet (tshark.c:3527)
==31263== by 0x40C837: main (tshark.c:3315)
==31263==
==31263==
==31263== HEAP SUMMARY:
==31263== in use at exit: 1,216,069 bytes in 29,624 blocks
==31263== total heap usage: 248,576 allocs, 218,952 frees, 30,028,258 bytes
allocated
==31263==
==31263== LEAK SUMMARY:
==31263== definitely lost: 3,656 bytes in 156 blocks
==31263== indirectly lost: 36,744 bytes in 51 blocks
==31263== possibly lost: 0 bytes in 0 blocks
==31263== still reachable: 1,175,669 bytes in 29,417 blocks
==31263== suppressed: 0 bytes in 0 blocks
==31263== Rerun with --leak-check=full to see details of leaked memory
==31263==
==31263== For counts of detected and suppressed errors, rerun with: -v
==31263== ERROR SUMMARY: 771 errors from 1 contexts (suppressed: 0 from 0)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.