| Bug ID |
13186
|
| Summary |
Buildbot crash output: fuzz-2016-11-28-2043.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-11-28-2043.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-11-28-2043.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/SMB-locking.pcapng.gz
Build host information:
Linux wsbb04 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 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=233
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.0/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=0eed3601fd0cde339591f261c5691d657074630c
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 0eed3601fd0cde339591f261c5691d657074630c
Author: Gerald Combs <[email protected]>
Date: Sun Nov 27 08:33:42 2016 -0800
[Automatic update for 2016-11-27]
Update manuf, services enterprise-numbers, translations, and other items.
Change-Id: Iec2b567d085a733aab43fc54bc54785315a76faa
Reviewed-on: https://code.wireshark.org/review/18966
Reviewed-by: Gerald Combs <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh
==15082== Memcheck, a memory error detector
==15082== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==15082== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==15082== Command:
/home/wireshark/builders/wireshark-2.0-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.0/fuzz-2016-11-28-2043.pcap
==15082==
==15082==
==15082== HEAP SUMMARY:
==15082== in use at exit: 1,098,121 bytes in 32,298 blocks
==15082== total heap usage: 7,508,261 allocs, 7,475,963 frees, 400,580,810
bytes allocated
==15082==
==15082== LEAK SUMMARY:
==15082== definitely lost: 36,892 bytes in 2,249 blocks
==15082== indirectly lost: 65,552 bytes in 1,867 blocks
==15082== possibly lost: 0 bytes in 0 blocks
==15082== still reachable: 995,677 bytes in 28,182 blocks
==15082== suppressed: 0 bytes in 0 blocks
==15082== Rerun with --leak-check=full to see details of leaked memory
==15082==
==15082== For counts of detected and suppressed errors, rerun with: -v
==15082== 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.