Bug ID |
11048
|
Summary |
Buildbot crash output: fuzz-2015-03-10-17539.pcap
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
URL |
https://www.wireshark.org/download/automated/captures/fuzz-2015-03-10-17539.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-2015-03-10-17539.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/13060-qnx640_withqnx641.cap
Build host information:
Linux wsbb04 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=3173
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=54c301a0d61a31b0a0469d8d9346b51af37c0009
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 54c301a0d61a31b0a0469d8d9346b51af37c0009
Author: Gerald Combs <[email protected]>
Date: Sun Mar 8 10:41:13 2015 -0700
Add the @2x expert indicators.
We currently load the expert indicator resources using an <img> tag.
According to QTBUG-36383 the @2x versions won't load unless you've built
with Qt 5.4.0 or later.
Change-Id: I003fd5d5f10e779f2e7ca6ba9fbb8e033df85b80
Reviewed-on: https://code.wireshark.org/review/7601
Reviewed-by: Gerald Combs <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh
==6904== Memcheck, a memory error detector
==6904== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==6904== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==6904== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2015-03-10-17539.pcap
==6904==
==6904== Invalid read of size 1
==6904== at 0x6CE2D91: dissect_qnet6 (packet-qnet6.c:1618)
==6904== by 0x671B83E: call_dissector_through_handle (packet.c:612)
==6904== by 0x671C1D4: call_dissector_work (packet.c:700)
==6904== by 0x671C91B: dissector_try_uint_new (packet.c:1132)
==6904== by 0x671C966: dissector_try_uint (packet.c:1158)
==6904== by 0x69AEA32: dissect_ethertype (packet-ethertype.c:300)
==6904== by 0x671B83E: call_dissector_through_handle (packet.c:612)
==6904== by 0x671C1D4: call_dissector_work (packet.c:700)
==6904== by 0x671DE51: call_dissector_with_data (packet.c:2386)
==6904== by 0x69AD374: dissect_eth_common (packet-eth.c:544)
==6904== by 0x671B803: call_dissector_through_handle (packet.c:614)
==6904== by 0x671C1D4: call_dissector_work (packet.c:700)
==6904== Address 0x12187791 is 0 bytes after a block of size 1 alloc'd
==6904== at 0x4C2CE8E: realloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==6904== by 0x9C406AE: g_realloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4002.0)
==6904== by 0x72700C0: wmem_simple_realloc (wmem_allocator_simple.c:90)
==6904== by 0x727167C: wmem_strbuf_finalize (wmem_strbuf.c:252)
==6904== by 0x6CE1D5C: dissect_qnet6 (packet-qnet6.c:1585)
==6904== by 0x671B83E: call_dissector_through_handle (packet.c:612)
==6904== by 0x671C1D4: call_dissector_work (packet.c:700)
==6904== by 0x671C91B: dissector_try_uint_new (packet.c:1132)
==6904== by 0x671C966: dissector_try_uint (packet.c:1158)
==6904== by 0x69AEA32: dissect_ethertype (packet-ethertype.c:300)
==6904== by 0x671B83E: call_dissector_through_handle (packet.c:612)
==6904== by 0x671C1D4: call_dissector_work (packet.c:700)
==6904==
==6904==
==6904== HEAP SUMMARY:
==6904== in use at exit: 1,221,187 bytes in 29,815 blocks
==6904== total heap usage: 256,686 allocs, 226,871 frees, 31,156,341 bytes
allocated
==6904==
==6904== LEAK SUMMARY:
==6904== definitely lost: 3,320 bytes in 142 blocks
==6904== indirectly lost: 36,968 bytes in 51 blocks
==6904== possibly lost: 0 bytes in 0 blocks
==6904== still reachable: 1,180,899 bytes in 29,622 blocks
==6904== suppressed: 0 bytes in 0 blocks
==6904== Rerun with --leak-check=full to see details of leaked memory
==6904==
==6904== For counts of detected and suppressed errors, rerun with: -v
==6904== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.