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 20:58:24 +0000 [thread overview]
Message-ID: <bug-28715-10460-8xhus6pn3v@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 #8 from Evgeny Vereshchagin <evvers at ya dot ru> ---
(In reply to Mark Wielaard from comment #7)
> (In reply to Evgeny Vereshchagin from comment #2)
> > 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?
>
> All patches sent to the list are also in patchwork:
> https://patchwork.sourceware.org/project/elfutils/list/
>
> I keep work in progress also in branch in my own git tree:
> https://code.wildebeest.org/git/user/mjw/elfutils/
>
> The fuzz branch has all recent patches based on your fuzzing reports and my
> own finds running afl and afl++ on amd64 and i686 for eu-stack --core
>
With https://code.wildebeest.org/git/user/mjw/elfutils/log/?h=fuzz rebased on
top of my "fuzzing" branch I can no longer reproduce this issue. Thanks!
> I think it is better if the reports were public.
Got it. I'll flip the flag there then. Would it be OK if I added your email
address to
https://github.com/google/oss-fuzz/blob/master/projects/elfutils/project.yaml
so that you could be notified when new bug reports were opened?
> But I think google really
> should just report these issues upstream instead of hiding them in their own
> bug tracker.
Unfortunately I can't change that (and I'm not affiliated with Google in any
way). I tried to use my main email address there but at some point I had to
create a gmail account to be able to look at systemd bug reports.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-20 20:58 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
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 [this message]
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-8xhus6pn3v@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).