From: "evvers at ya dot ru" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/28715] There seems to be an infinite loop in dwfl_segment_report_module
Date: Mon, 20 Dec 2021 02:40:49 +0000 [thread overview]
Message-ID: <bug-28715-10460-ZvmtHIytSF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28715-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28715
--- Comment #2 from Evgeny Vereshchagin <evvers at ya dot ru> ---
(In reply to Mark Wielaard from comment #1)
> I couldn't replicate the infinite loop, which I assume has been fixed by:
> https://sourceware.org/pipermail/elfutils-devel/2021q4/004557.html
>
> But I saw it did trigger yet another xlate alignment issue for which I did
> submit:
> https://sourceware.org/pipermail/elfutils-devel/2021q4/004565.html
Thanks! I'll try to take a look tomorrow.
There seem to be quite a few new patches on the mailing list. I wonder if it's
possible to somehow fetch a branch with all of them so that I could just rebase
the fuzzing infrastructure on top of it?
> P.S. Note that the bugs.chromium.org link doesn't work for me, it apparently
> requires a google account with permissions to even just look at that bug.
It's possible to make all the bug reports public by default. For example, in
https://github.com/google/oss-fuzz/pull/6741 the PHP project decided that bug
reports should be no longer restricted and flipped the flag. I can do the same
but I don't think I can do it without your approval.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-20 2:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 20:41 [Bug libdw/28715] New: " evvers at ya dot ru
2021-12-20 0:44 ` [Bug libdw/28715] " mark at klomp dot org
2021-12-20 2:40 ` evvers at ya dot ru [this message]
2021-12-20 11:41 ` evvers at ya dot ru
2021-12-20 15:39 ` evvers at ya dot ru
2021-12-20 15:47 ` evvers at ya dot ru
2021-12-20 17:25 ` mark at klomp dot org
2021-12-20 17:38 ` mark at klomp dot org
2021-12-20 20:58 ` evvers at ya dot ru
2021-12-21 11:17 ` mark at klomp dot org
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=bug-28715-10460-ZvmtHIytSF@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/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).