| Bug ID |
12871
|
| Summary |
Buildbot crash output: fuzz-2016-09-11-10657.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-09-11-10657.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-2016-09-11-10657.pcap
stderr:
Input file:
/home/wireshark/menagerie/menagerie/14385-Wireshark_Community_Capture.pcap
Build host information:
Linux wsbb04 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=81
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=46000416505cda02d3fa4daa0701c7828789583d
Return value: 152
Dissector bug: 0
Valgrind error count: 0
Git commit
commit 46000416505cda02d3fa4daa0701c7828789583d
Author: Gerald Combs <[email protected]>
Date: Fri Sep 9 15:04:15 2016 -0700
PortableApps: Allow multiple instances.
The documentation for the [Launch]SingleAppInstance key doesn't seem
to match its behavior in that its default value (true) keeps multiple
portable instances from running, at least for us. Set it to false since
we're happy with users running as many concurrent instances as they can
stand. Set the related SinglePortableAppInstance key to false while
we're here in case its default value ever changes.
Change-Id: Iea1a6a80d5b204814b7569776734e0b0e254d657
Reviewed-on: https://code.wireshark.org/review/17617
Reviewed-by: Gerald Combs <[email protected]>
==20779== Memcheck, a memory error detector
==20779== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==20779== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==20779== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-09-11-10657.pcap
==20779==
==20779==
==20779== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==20779== at 0xF525C04: dissect_PNIO_C_SDU_RTC1 (packet-pn-rtc-one.c:702)
==20779== by 0xF5111DC: dissect_PNIO_heur (packet-dcerpc-pn-io.c:10308)
==20779== by 0x69494BF: dissector_try_heuristic (packet.c:2429)
==20779== by 0xF523FEA: dissect_pn_rt (packet-pn-rt.c:801)
==20779== by 0x69480FE: call_dissector_through_handle (packet.c:648)
==20779== by 0x69480FE: call_dissector_work (packet.c:723)
==20779== by 0x6948828: dissector_try_uint_new (packet.c:1188)
==20779== by 0x6948870: dissector_try_uint (packet.c:1214)
==20779== by 0x6C15E82: dissect_ethertype (packet-ethertype.c:262)
==20779== by 0x69480FE: call_dissector_through_handle (packet.c:648)
==20779== by 0x69480FE: call_dissector_work (packet.c:723)
==20779== by 0x6949B31: call_dissector_with_data (packet.c:2816)
==20779== by 0x6C14764: dissect_eth_common (packet-eth.c:539)
==20779== by 0x6C15300: dissect_eth (packet-eth.c:803)
==20779==
==20779== HEAP SUMMARY:
==20779== in use at exit: 20,015,066 bytes in 215,137 blocks
==20779== total heap usage: 1,650,545 allocs, 1,435,408 frees, 74,650,648
bytes allocated
==20779==
==20779== LEAK SUMMARY:
==20779== definitely lost: 343 bytes in 20 blocks
==20779== indirectly lost: 362 bytes in 4 blocks
==20779== possibly lost: 0 bytes in 0 blocks
==20779== still reachable: 20,014,361 bytes in 215,113 blocks
==20779== suppressed: 0 bytes in 0 blocks
==20779== Rerun with --leak-check=full to see details of leaked memory
==20779==
==20779== For counts of detected and suppressed errors, rerun with: -v
==20779== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
./tools/valgrind-wireshark.sh: line 123: 20779 CPU time limit exceeded (core
dumped) $cmdline > /dev/null
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.
