public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28224] Use-after-free when calling a GNU ifunc Date: Sun, 06 Mar 2022 17:18:25 +0000 [thread overview] Message-ID: <bug-28224-4717-zp0oXrYU0E@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28224-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28224 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- + frame = get_current_frame (); Jan pointed out ages ago that the gdb design where a frame can be silently invalidated by some calls -- and so the caller has to store a frame-id and "reinflate" the frame -- is fragile. One idea we've discussed is to use C++ objects for these things, so that when a frame is invalidated, it will reinflate all on its own, on reference. Then the callers don't need to be handled specially. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-06 17:18 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 ` tromey at sourceware dot org [this message] 2022-05-08 13:46 ` [Bug gdb/28224] " ssbssa at sourceware dot org 2022-05-08 17:12 ` simark at simark dot ca 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-zp0oXrYU0E@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: linkBe 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).