| Bug ID |
12717
|
| Summary |
Buildbot crash output: fuzz-2016-08-07-10022.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-08-07-10022.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-08-07-10022.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.cap
Build host information:
Linux wsbb04 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 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=27
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=7dd70ca1b4de1b1a6b93c140d144ffee50330c1a
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 7dd70ca1b4de1b1a6b93c140d144ffee50330c1a
Author: Dario Lombardo <[email protected]>
Date: Fri Aug 5 22:00:05 2016 +0200
doc: fix typos.
Change-Id: Id34affcb33c00e224dafbccc347b1d91b9e74c8d
Reviewed-on: https://code.wireshark.org/review/16914
Reviewed-by: Michael Mann <[email protected]>
(cherry picked from commit 37649c4d0f0e3c87308687f9000dbe9f627594de)
Reviewed-on: https://code.wireshark.org/review/16923
==10052== Memcheck, a memory error detector
==10052== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==10052== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==10052== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-07-10022.pcap
==10052==
==10052==
==10052== HEAP SUMMARY:
==10052== in use at exit: 1,505,019 bytes in 39,703 blocks
==10052== total heap usage: 264,991 allocs, 225,288 frees, 30,561,819 bytes
allocated
==10052==
==10052== LEAK SUMMARY:
==10052== definitely lost: 332,998 bytes in 150 blocks
==10052== indirectly lost: 726,256 bytes in 29,958 blocks
==10052== possibly lost: 0 bytes in 0 blocks
==10052== still reachable: 445,765 bytes in 9,595 blocks
==10052== suppressed: 0 bytes in 0 blocks
==10052== Rerun with --leak-check=full to see details of leaked memory
==10052==
==10052== For counts of detected and suppressed errors, rerun with: -v
==10052== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.
