public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Evgeny Vereshchagin <evverx@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: oss-fuzz@monorail-prod.appspotmail.com,
	elfutils-devel@sourceware.org,
	 ClusterFuzz-External via monorail
	<monorail+v2.382749006@chromium.org>
Subject: Re: Issue 55999 in oss-fuzz: elfutils: Fuzzing build failure
Date: Wed, 15 Feb 2023 20:07:48 +0300	[thread overview]
Message-ID: <CAKKs9ugqB_1RWj1-M1+YjMgT8aA6nCwmc=H-oY4vBsiw35JwTA@mail.gmail.com> (raw)
In-Reply-To: <4398d0786626e419e5d0f92bf7d5e366634cd5d7.camel@klomp.org>

Hi Mark,

I fixed the build failure in
https://github.com/google/oss-fuzz/pull/9718. Once it's merged
and reaches ClusterFuzz OSS-Fuzz should close the issue.

> Note that we also recently got support for --enable-sanitize-memory but
> that needs a bit of setup and only works with the clang compiler. See
> https://inbox.sourceware.org/elfutils-devel/6e576e707fa3da14f4e9045cbf53ba887823a543.camel@linux.ibm.com/T/

Thanks! It helped to pinpoint the issue. I think it would be better if
it was possible to turn off --no-undefined
separately to make it easier to build elfutils on OSS-Fuzz (where I
can't pass `--enable-sanitize-*`) and avoid
build failures like that going forward. It was discussed in
https://sourceware.org/pipermail/elfutils-devel/2021q4/004418.html
but didn't go anywhere though.

Thanks,
Evgeny Vereshchagin

  reply	other threads:[~2023-02-15 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ce7b5f861c1a0d42714a49e3059f172a=oss-fuzz@monorail-prod.appspotmail.com>
2023-02-15 12:01 ` ClusterFuzz-External via monorail
2023-02-15 12:32   ` Mark Wielaard
2023-02-15 17:07     ` Evgeny Vereshchagin [this message]
2023-02-16 13:23       ` Mark Wielaard
2023-02-16 15:27         ` Evgeny Vereshchagin
2023-02-16  6:01 ` 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='CAKKs9ugqB_1RWj1-M1+YjMgT8aA6nCwmc=H-oY4vBsiw35JwTA@mail.gmail.com' \
    --to=evverx@gmail.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.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).