public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28224] Use-after-free when calling a GNU ifunc
Date: Sun, 08 May 2022 17:12:05 +0000 [thread overview]
Message-ID: <bug-28224-4717-by0nGOb23N@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28224-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28224
--- Comment #3 from Simon Marchi <simark at simark dot ca> ---
(In reply to Hannes Domani from comment #2)
> Isn't this a duplicate of PR27683?
Yeah, I had an impression of deja vu when replying to #27683. I will mark
#27683 duplicate of this one, since this one has a bit more analysis. But it
would be nice to test the reproducer in #27683 when coming up with a fix.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-08 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 21:10 [Bug gdb/28224] New: " simark at simark dot ca
2022-03-06 17:18 ` [Bug gdb/28224] " tromey at sourceware dot org
2022-05-08 13:46 ` ssbssa at sourceware dot org
2022-05-08 17:12 ` simark at simark dot ca [this message]
2022-05-08 17:12 ` simark at simark dot ca
2022-12-26 13:08 ` vries at gcc dot gnu.org
2022-12-26 13:13 ` vries at gcc dot gnu.org
2022-12-26 13:13 ` vries at gcc dot gnu.org
2022-12-26 13:18 ` vries at gcc dot gnu.org
2022-12-26 15:15 ` philippe.waroquiers at skynet dot be
2022-12-26 22:02 ` mark at klomp dot org
2022-12-27 3:26 ` simark at simark dot ca
2022-12-27 5:25 ` vries at gcc dot gnu.org
2022-12-27 7:24 ` vries at gcc dot gnu.org
2022-12-27 9:56 ` vries at gcc dot gnu.org
2023-01-03 10:54 ` vries at gcc dot gnu.org
2023-01-07 11:07 ` brobecker at gnat dot com
2023-01-07 12:21 ` vries at gcc dot gnu.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-28224-4717-by0nGOb23N@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).