| Bug ID |
12078
|
| Summary |
Buildbot crash output: fuzz-2016-02-02-1153.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-02-02-1153.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-02-02-1153.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/ndsp_v2.pcapng.gz
Build host information:
Linux wsbb04 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty
Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_BUILDNUMBER=3485
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=26a24ba6c6912d584d6a5b5d7e8b79643718bb93
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 26a24ba6c6912d584d6a5b5d7e8b79643718bb93
Author: Gerald Combs <[email protected]>
Date: Sun Jan 31 08:05:46 2016 -0800
[Automatic update for 2016-01-31]
Update manuf, services enterprise-numbers, translations, and other items.
Change-Id: I7e8ade92cce819240ee8e40cfc63363185d9d944
Reviewed-on: https://code.wireshark.org/review/13625
Reviewed-by: Gerald Combs <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh
==6631== Memcheck, a memory error detector
==6631== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==6631== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==6631== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2016-02-02-1153.pcap
==6631==
==6631==
==6631== HEAP SUMMARY:
==6631== in use at exit: 1,119,301 bytes in 32,630 blocks
==6631== total heap usage: 592,797 allocs, 560,167 frees, 45,678,853 bytes
allocated
==6631==
==6631== LEAK SUMMARY:
==6631== definitely lost: 64,308 bytes in 3,955 blocks
==6631== indirectly lost: 38,888 bytes in 139 blocks
==6631== possibly lost: 0 bytes in 0 blocks
==6631== still reachable: 1,016,105 bytes in 28,536 blocks
==6631== suppressed: 0 bytes in 0 blocks
==6631== Rerun with --leak-check=full to see details of leaked memory
==6631==
==6631== For counts of detected and suppressed errors, rerun with: -v
==6631== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.
