| Bug ID |
12784
|
| Summary |
Buildbot crash output: fuzz-2016-08-24-17811.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-08-24-17811.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-24-17811.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/10484-frame31.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=52
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=96e712f91ffdef5f0c95ed4d848e4ead14cf7522
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 96e712f91ffdef5f0c95ed4d848e4ead14cf7522
Author: Gerald Combs <[email protected]>
Date: Tue Aug 23 10:44:32 2016 -0700
Update the release notes.
Add missing new protocols, move a "what's new item", add a bug.
Change-Id: I84e4cf36591a503d96032c6be9ba14bdc0dc016c
Reviewed-on: https://code.wireshark.org/review/17273
Petri-Dish: Gerald Combs <[email protected]>
Tested-by: Petri Dish Buildbot <[email protected]>
Reviewed-by: Gerald Combs <[email protected]>
==20470== Memcheck, a memory error detector
==20470== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==20470== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==20470== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-24-17811.pcap
==20470==
==20470==
==20470== HEAP SUMMARY:
==20470== in use at exit: 858,873 bytes in 26,970 blocks
==20470== total heap usage: 296,385 allocs, 269,415 frees, 36,481,428 bytes
allocated
==20470==
==20470== LEAK SUMMARY:
==20470== definitely lost: 3,367 bytes in 150 blocks
==20470== indirectly lost: 405,530 bytes in 17,121 blocks
==20470== possibly lost: 0 bytes in 0 blocks
==20470== still reachable: 449,976 bytes in 9,699 blocks
==20470== suppressed: 0 bytes in 0 blocks
==20470== Rerun with --leak-check=full to see details of leaked memory
==20470==
==20470== For counts of detected and suppressed errors, rerun with: -v
==20470== 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.
