| Bug ID |
12786
|
| Summary |
Buildbot crash output: fuzz-2016-08-25-6141.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-08-25-6141.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-25-6141.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-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=53
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=1c1610597b3a166bf3cd669345f9408e8b06ccbe
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 1c1610597b3a166bf3cd669345f9408e8b06ccbe
Author: Gerald Combs <[email protected]>
Date: Tue Aug 23 16:55:16 2016 -0700
Fuzz test: Make Valgrind error detection more verbose.
When we set VG_ERR_CNT=1 print the reason.
Change-Id: Icb8f2a1e7074044521873b116fc891cc4be4b204
Reviewed-on: https://code.wireshark.org/review/17286
Reviewed-by: Gerald Combs <[email protected]>
==7373== Memcheck, a memory error detector
==7373== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==7373== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==7373== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-25-6141.pcap
==7373==
==7373==
==7373== HEAP SUMMARY:
==7373== in use at exit: 2,036,758 bytes in 46,075 blocks
==7373== total heap usage: 416,404 allocs, 370,329 frees, 48,528,884 bytes
allocated
==7373==
==7373== LEAK SUMMARY:
==7373== definitely lost: 3,554 bytes in 157 blocks
==7373== indirectly lost: 405,722 bytes in 17,126 blocks
==7373== possibly lost: 0 bytes in 0 blocks
==7373== still reachable: 1,627,482 bytes in 28,792 blocks
==7373== suppressed: 0 bytes in 0 blocks
==7373== Rerun with --leak-check=full to see details of leaked memory
==7373==
==7373== For counts of detected and suppressed errors, rerun with: -v
==7373== 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.
