| Bug ID |
12809
|
| Summary |
Buildbot crash output: fuzz-2016-09-01-25678.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-09-01-25678.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-01-25678.pcap
stderr:
Input file:
/home/wireshark/menagerie/menagerie/10783-traces_lass-pc-8.10.1.cap.gz
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=69
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=a07560271a3e21ec374f55ba4ee02cb1cbab43b9
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit a07560271a3e21ec374f55ba4ee02cb1cbab43b9
Author: Gerald Combs <[email protected]>
Date: Wed Aug 31 12:45:41 2016 -0700
2.2.0rc2 → 2.2.0rc3.
Change-Id: I1c4f6a2857534aff6cfb01d7102edbd8140e759d
Reviewed-on: https://code.wireshark.org/review/17427
Reviewed-by: Gerald Combs <[email protected]>
==17040== Memcheck, a memory error detector
==17040== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==17040== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==17040== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-09-01-25678.pcap
==17040==
==17040==
==17040== HEAP SUMMARY:
==17040== in use at exit: 2,036,473 bytes in 46,074 blocks
==17040== total heap usage: 413,838 allocs, 367,764 frees, 48,523,453 bytes
allocated
==17040==
==17040== LEAK SUMMARY:
==17040== definitely lost: 3,554 bytes in 157 blocks
==17040== indirectly lost: 405,690 bytes in 17,124 blocks
==17040== possibly lost: 0 bytes in 0 blocks
==17040== still reachable: 1,627,229 bytes in 28,793 blocks
==17040== suppressed: 0 bytes in 0 blocks
==17040== Rerun with --leak-check=full to see details of leaked memory
==17040==
==17040== For counts of detected and suppressed errors, rerun with: -v
==17040== 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.