| Bug ID |
11293
|
| Summary |
Buildbot crash output: fuzz-2015-06-20-12610.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2015-06-20-12610.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-2015-06-20-12610.pcap
stderr:
Input file:
/home/wireshark/menagerie/menagerie/13669-running12_00036_20150616114139.pcapng
Build host information:
Linux wsbb04 3.13.0-55-generic #92-Ubuntu SMP Sun Jun 14 18:32:20 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=3259
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=d8529ba64de81b52cefa536f5020415b57042623
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit d8529ba64de81b52cefa536f5020415b57042623
Author: Joerg Mayer <[email protected]>
Date: Thu Jun 18 16:48:42 2015 +0200
Add ExtremeNetworks attribute 213 (and the source of the information)
Change-Id: I2fe561eef38ecc31693270b527af1f42ef564734
Reviewed-on: https://code.wireshark.org/review/8977
Reviewed-by: Jörg Mayer <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh -T
==31513== Memcheck, a memory error detector
==31513== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==31513== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright
info
==31513== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2015-06-20-12610.pcap
==31513==
==31513==
==31513== HEAP SUMMARY:
==31513== in use at exit: 2,363,796 bytes in 178,205 blocks
==31513== total heap usage: 2,928,375 allocs, 2,750,170 frees, 212,243,817
bytes allocated
==31513==
==31513== LEAK SUMMARY:
==31513== definitely lost: 128,180 bytes in 15,742 blocks
==31513== indirectly lost: 37,320 bytes in 53 blocks
==31513== possibly lost: 0 bytes in 0 blocks
==31513== still reachable: 2,198,296 bytes in 162,410 blocks
==31513== suppressed: 0 bytes in 0 blocks
==31513== Rerun with --leak-check=full to see details of leaked memory
==31513==
==31513== For counts of detected and suppressed errors, rerun with: -v
==31513== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.