From: Alan Modra <amodra@gmail.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: binutils@sourceware.org
Subject: Re: timeout in mmo_get_symbols
Date: Wed, 17 Aug 2022 23:12:28 +0930 [thread overview]
Message-ID: <YvzwREBWN9ON3/6u@squeak.grove.modra.org> (raw)
In-Reply-To: <alpine.BSF.2.20.16.2208170725140.20497@arjuna.pair.com>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
On Wed, Aug 17, 2022 at 07:29:03AM -0400, Hans-Peter Nilsson wrote:
> Thanks for the fuzzer mmo fixes.
> I have to ask, about the subject, "timeout"?
> Did this bug perhaps cause an infinite loop with some fuzzed
> object?
Yes. https://oss-fuzz.com/testcase-detail/5712821022752768
(That link might not work until their next build when it should be
seen to be fixed and thus open to the public.)
Testcase attached too.
--
Alan Modra
Australia Development Lab, IBM
[-- Attachment #2: clusterfuzz-testcase-minimized-fuzz_dwarf-5712821022752768 --]
[-- Type: application/octet-stream, Size: 708 bytes --]
prev parent reply other threads:[~2022-08-17 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 7:08 Alan Modra
2022-08-17 11:29 ` Hans-Peter Nilsson
2022-08-17 13:42 ` Alan Modra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YvzwREBWN9ON3/6u@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hp@bitrange.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).