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 43505 in oss-fuzz: elfutils:fuzz-dwfl-core: Use-of-uninitialized-value in handle_file_note
Date: Thu, 17 Mar 2022 01:49:46 +0100	[thread overview]
Message-ID: <YjKFqu3DTKF+zOZK@wildebeest.org> (raw)
In-Reply-To: <000000000000e577fa05da5f3e74@google.com>

Hi,

Does anybody know why/where these message suddenly come from?
There have now been multiple today and yesterday.
Unfortunately the reply-to address seems to just bounce any of my replies.

On Wed, Mar 16, 2022 at 05:38:15PM -0700, ClusterFuzz-External via monorail via Elfutils-devel wrote:
> Comment #4 on issue 43505 by ClusterFuzz-External: elfutils:fuzz-dwfl-core: Use-of-uninitialized-value in handle_file_note
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43505#c4

As one of the comments in this bug report says "it seems MSan doesn't
like unions that aren't initialized explicitly".

But the backtrace given in the report doesn't seem to match the
current elfutils code. So maybe this is against some old elfutils
version?

Cheers,

Mark


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=2c0356afc660f9c3dfa1ade2a69ce6ad=oss-fuzz@monorail-prod.appspotmail.com>
2022-01-10 16:24 ` ClusterFuzz-External via monorail
2022-01-10 17:33 ` ClusterFuzz-External via monorail
2022-01-10 18:47 ` evv… via monorail
2022-01-12 22:37 ` evv… via monorail
2022-03-17  0:38 ` ClusterFuzz-External via monorail
2022-03-17  0:49   ` Mark Wielaard [this message]
2022-03-23 15:32 ` 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=YjKFqu3DTKF+zOZK@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).