https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14736
Bug ID: 14736
Summary: Buildbot crash output: fuzz-2018-05-25-19272.pcap
Product: Wireshark
Version: unspecified
Hardware: x86-64
OS: Ubuntu
Status: CONFIRMED
Severity: Major
Priority: High
Component: Dissection engine (libwireshark)
Assignee: bugzilla-ad...@wireshark.org
Reporter: buildbot-do-not-re...@wireshark.org
Target Milestone: ---
Problems have been found with the following capture file:
https://www.wireshark.org/download/automated/captures/fuzz-2018-05-25-19272.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/03-13_los_altos.pcap
Build host information:
Linux wsbb04 4.4.0-127-generic #153-Ubuntu SMP Sat May 19 10:58:46 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial
Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-build...@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=4773
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=bf8590326a5477a3211bc7498d8a48e90e5d49da
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit bf8590326a5477a3211bc7498d8a48e90e5d49da
Author: Dirk Eibach <dirk.eib...@gdsys.cc>
Date: Fri May 25 21:14:52 2018 +0200
dpa400: Fix wiretap data packet len
Increment the packet size whenn adding the from_source field.
Change-Id: I380305d763df40b2cf1f2209643d05dfde12a716
Reviewed-on: https://code.wireshark.org/review/27811
Reviewed-by: Guy Harris <g...@alum.mit.edu>
==30625== Memcheck, a memory error detector
==30625== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==30625== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==30625== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-Vx -nr
/fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2018-05-25-19272.pcap
==30625==
==30625==
==30625== HEAP SUMMARY:
==30625== in use at exit: 3,910,964 bytes in 2,288 blocks
==30625== total heap usage: 8,739,074 allocs, 8,736,786 frees, 638,268,464
bytes allocated
==30625==
==30625== LEAK SUMMARY:
==30625== definitely lost: 3,795,744 bytes in 1,865 blocks
==30625== indirectly lost: 4,818 bytes in 182 blocks
==30625== possibly lost: 2,048 bytes in 1 blocks
==30625== still reachable: 15,899 bytes in 186 blocks
==30625== suppressed: 92,455 bytes in 54 blocks
==30625== Rerun with --leak-check=full to see details of leaked memory
==30625==
==30625== For counts of detected and suppressed errors, rerun with: -v
==30625== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Definitely + indirectly (3795744 + 4818) exceeds max (102400).
[ no debug trace ]
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
