From: ClusterFuzz-External via monorail <monorail+v2.382749006@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 62071 in oss-fuzz: elfutils:fuzz-libdwfl: Null-dereference READ in chunk_compare
Date: Wed, 20 Sep 2023 00:52:29 -0700 [thread overview]
Message-ID: <0000000000003e723f0605c5a84b@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=1491f90a54bd791097d19cec88a861b0=oss-fuzz@monorail-prod.appspotmail.com>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Updates:
Status: WontFix
Comment #3 on issue 62071 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Null-dereference READ in chunk_compare
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071#c3
ClusterFuzz testcase 5999675550072832 is flaky and no longer crashes, so closing issue.
If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
next prev parent reply other threads:[~2023-09-20 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=1491f90a54bd791097d19cec88a861b0=oss-fuzz@monorail-prod.appspotmail.com>
2023-09-06 5:01 ` ClusterFuzz-External via monorail
2023-09-07 9:38 ` Mark Wielaard
2023-09-07 12:31 ` evv… via monorail
2023-09-07 12:36 ` Mark Wielaard
2023-09-07 13:23 ` evv… via monorail
2023-09-07 14:25 ` Mark Wielaard
2023-09-11 7:42 ` Mark Wielaard
2023-09-20 7:52 ` ClusterFuzz-External via monorail [this message]
2023-09-20 7:52 ` ClusterFuzz-External via monorail
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=0000000000003e723f0605c5a84b@google.com \
--to=monorail+v2.382749006@chromium.org \
--cc=elfutils-devel@sourceware.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).