Bug ID |
10883
|
Summary |
Buildbot crash output: fuzz-2015-01-21-15160.pcap
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
URL |
https://www.wireshark.org/download/automated/captures/fuzz-2015-01-21-15160.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-01-21-15160.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/c06-snmpv1-req-app-r1.pcap.gz
Build host information:
Linux wsbb04 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=3116
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=c3ad53f9ad9c060a7079c0f8f93f3e99af5c77af
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit c3ad53f9ad9c060a7079c0f8f93f3e99af5c77af
Author: Guy Harris <[email protected]>
Date: Mon Jan 19 16:47:55 2015 -0800
Fix one item.
We *do* get the absolute path of the executable, so we *could* look for
"run" right before the executable name. The issue is that there's not
the stronger libtool-imposed convention that the executable is in
".libs", so the chances of a false positive or false negative are
higher.
Change-Id: Ib2d5f370d50fee07479c4ffe6f90ba4a91c7f271
Reviewed-on: https://code.wireshark.org/review/6676
Reviewed-by: Guy Harris <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh -T
==11056== Memcheck, a memory error detector
==11056== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==11056== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright
info
==11056== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2015-01-21-15160.pcap
==11056==
==11056==
==11056== HEAP SUMMARY:
==11056== in use at exit: 1,334,633 bytes in 30,341 blocks
==11056== total heap usage: 3,989,352 allocs, 3,959,011 frees, 342,586,818
bytes allocated
==11056==
==11056== LEAK SUMMARY:
==11056== definitely lost: 70,576 bytes in 772 blocks
==11056== indirectly lost: 36,744 bytes in 51 blocks
==11056== possibly lost: 0 bytes in 0 blocks
==11056== still reachable: 1,227,313 bytes in 29,518 blocks
==11056== suppressed: 0 bytes in 0 blocks
==11056== Rerun with --leak-check=full to see details of leaked memory
==11056==
==11056== For counts of detected and suppressed errors, rerun with: -v
==11056== 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.