Bug ID |
12777
|
Summary |
Buildbot crash output: fuzz-2016-08-23-1137.pcap
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-08-23-1137.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-23-1137.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=48
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=e388dd0e6d81ef344d55f84f4dddd8bb78d2c3c9
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit e388dd0e6d81ef344d55f84f4dddd8bb78d2c3c9
Author: Guy Harris <[email protected]>
Date: Sun Aug 21 23:36:54 2016 -0700
Get rid of trailing blank line.
Change-Id: I409a843b48983355c242708f6c9972bd8f337bf6
Reviewed-on: https://code.wireshark.org/review/17218
Reviewed-by: Guy Harris <[email protected]>
(cherry picked from commit e1f11c97349dad879c3d3a875c289a195a8ba52c)
Reviewed-on: https://code.wireshark.org/review/17220
==4459== Memcheck, a memory error detector
==4459== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==4459== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==4459== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-23-1137.pcap
==4459==
==4459==
==4459== HEAP SUMMARY:
==4459== in use at exit: 2,036,689 bytes in 46,071 blocks
==4459== total heap usage: 420,105 allocs, 374,034 frees, 48,562,793 bytes
allocated
==4459==
==4459== LEAK SUMMARY:
==4459== definitely lost: 3,517 bytes in 155 blocks
==4459== indirectly lost: 405,690 bytes in 17,124 blocks
==4459== possibly lost: 0 bytes in 0 blocks
==4459== still reachable: 1,627,482 bytes in 28,792 blocks
==4459== suppressed: 0 bytes in 0 blocks
==4459== Rerun with --leak-check=full to see details of leaked memory
==4459==
==4459== For counts of detected and suppressed errors, rerun with: -v
==4459== 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.