| Bug ID |
12710
|
| Summary |
Buildbot crash output: fuzz-2016-08-04-9289.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-08-04-9289.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-04-9289.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.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=
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=24
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=b19a08874915bbf303a3b6d4b4df9b6e3799517b
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit b19a08874915bbf303a3b6d4b4df9b6e3799517b
Author: Roland Knall <[email protected]>
Date: Tue Aug 2 17:04:56 2016 +0200
openSAFETY: Add two checks for scm udid validity
This is being done, to prevent false-positives which can
not be filtered out using the heuristics, but have to be
caught using additional check measurements
Change-Id: I2ff2c97decf8a93d43f8f5b54e4d147552970b3f
Reviewed-on: https://code.wireshark.org/review/16843
Petri-Dish: Roland Knall <[email protected]>
Tested-by: Petri Dish Buildbot <[email protected]>
Reviewed-by: Roland Knall <[email protected]>
(cherry picked from commit e631e1156daa25671f4b61b92f9bee646866d0c2)
Reviewed-on: https://code.wireshark.org/review/16853
Reviewed-by: Anders Broman <[email protected]>
==9389== Memcheck, a memory error detector
==9389== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==9389== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==9389== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-04-9289.pcap
==9389==
==9389==
==9389== HEAP SUMMARY:
==9389== in use at exit: 1,505,138 bytes in 39,708 blocks
==9389== total heap usage: 264,843 allocs, 225,135 frees, 30,552,651 bytes
allocated
==9389==
==9389== LEAK SUMMARY:
==9389== definitely lost: 332,998 bytes in 150 blocks
==9389== indirectly lost: 726,376 bytes in 29,963 blocks
==9389== possibly lost: 0 bytes in 0 blocks
==9389== still reachable: 445,764 bytes in 9,595 blocks
==9389== suppressed: 0 bytes in 0 blocks
==9389== Rerun with --leak-check=full to see details of leaked memory
==9389==
==9389== For counts of detected and suppressed errors, rerun with: -v
==9389== 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.