https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14586
Bug ID: 14586
Summary: Buildbot crash output: fuzz-2018-04-04-16225.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-04-04-16225.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.cap
Build host information:
Linux wsbb04 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 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=fuzz-test
BUILDBOT_BUILDNUMBER=2
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.6/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=cf4a195ceff36472ab594115e618208185b6227f
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit cf4a195ceff36472ab594115e618208185b6227f
Author: Guy Harris <g...@alum.mit.edu>
Date: Mon Apr 2 18:03:30 2018 -0700
If we're reading from a string, don't fclose yyin.
yyin is initialized to stdin. When we're reading from files, we set it
so that it points to the FILE from which we're reading, but when we're
reading from a string, we don't set it, leaving it to point to stdin.
This means that, just as the "read from the input" routine has to be set
differently when reading from a file or a string, the "close the current
input" routine has to be set differently as well.
Bug: 14577
Change-Id: Ie05880775612867e9037ace2de0cd0a0dd2fabb5
Reviewed-on: https://code.wireshark.org/review/26719
Reviewed-by: Guy Harris <g...@alum.mit.edu>
(cherry picked from commit 9d87f607ee2ecefaff71f2ab3f2dc3d2dc185399)
Reviewed-on: https://code.wireshark.org/review/26720
==16404== Memcheck, a memory error detector
==16404== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==16404== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==16404== Command:
/home/wireshark/builders/wireshark-2.6-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.6/fuzz-2018-04-04-16225.pcap
==16404==
tshark: Couldn't load plugin 'l16mono.so':
/home/wireshark/builders/wireshark-2.6-fuzz/fuzztest/install/lib/wireshark/plugins/2.6/wiretap/l16mono.so:
undefined symbol: register_codec
==16404== Thread 2:
==16404== Conditional jump or move depends on uninitialised value(s)
==16404== at 0xA5C7FB6: ws_mempbrk_sse42_compile (ws_mempbrk_sse42.c:58)
==16404== by 0x6AFF1A0: register_all_protocols_worker (register.c:37)
==16404== by 0xAA4DBB4: ??? (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==16404== by 0xB45A6B9: start_thread (pthread_create.c:333)
==16404== by 0xB77741C: clone (clone.S:109)
==16404==
==16404==
==16404== HEAP SUMMARY:
==16404== in use at exit: 107,627 bytes in 144 blocks
==16404== total heap usage: 333,960 allocs, 333,816 frees, 38,472,724 bytes
allocated
==16404==
==16404== LEAK SUMMARY:
==16404== definitely lost: 0 bytes in 0 blocks
==16404== indirectly lost: 0 bytes in 0 blocks
==16404== possibly lost: 0 bytes in 0 blocks
==16404== still reachable: 13,304 bytes in 115 blocks
==16404== suppressed: 94,323 bytes in 29 blocks
==16404== Rerun with --leak-check=full to see details of leaked memory
==16404==
==16404== For counts of detected and suppressed errors, rerun with: -v
==16404== Use --track-origins=yes to see where uninitialised values come from
==16404== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
[ 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
