public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: oss-fuzz@monorail-prod.appspotmail.com
Cc: elfutils-devel@sourceware.org,
	ClusterFuzz-External via monorail
	<monorail+v2.382749006@chromium.org>
Subject: Re: Issue 43449 in oss-fuzz: elfutils:fuzz-dwfl-core: Timeout in fuzz-dwfl-core
Date: Thu, 17 Mar 2022 01:45:22 +0100	[thread overview]
Message-ID: <YjKEoj0HIOkpTU79@wildebeest.org> (raw)
In-Reply-To: <000000000000afa59705da5f3e2b@google.com>

Hi,

On Wed, Mar 16, 2022 at 05:38:11PM -0700, ClusterFuzz-External via monorail via Elfutils-devel wrote:
> Comment #2 on issue 43449 by ClusterFuzz-External: elfutils:fuzz-dwfl-core: Timeout in fuzz-dwfl-core
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43449#c2

As one of the comments on this says "it takes the fuzzer about 15
seconds to process this file without ASan so it doesn't seem to be an
elfutils issue".

15 seconds sounds like a very long time, especially without asan. ASAN
often takes a long time on 64bit arches. I would recommend to only use
it on 32bit targets if possible.

However it isn't clear to me what this "fuzz-dwfl-core" is, where the
source is and how to replicate this.

Cheers,

Mark


      reply	other threads:[~2022-03-17  0:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=f6ab5b08784fd51907747ae33cfb48be=oss-fuzz@monorail-prod.appspotmail.com>
2022-01-09  0:55 ` ClusterFuzz-External via monorail
2022-01-09 16:38 ` evv… via monorail
2022-03-17  0:38 ` ClusterFuzz-External via monorail
2022-03-17  0:45   ` Mark Wielaard [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=YjKEoj0HIOkpTU79@wildebeest.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=monorail+v2.382749006@chromium.org \
    --cc=oss-fuzz@monorail-prod.appspotmail.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).