public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23342] sanity check stale struct frame_info *
Date: Sat, 03 Apr 2021 20:49:34 +0000	[thread overview]
Message-ID: <bug-23342-4717-RTC2OP3OvU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23342-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23342

--- Comment #9 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
(In reply to Tom Tromey from comment #8)
> The proposed "reinflation" approach is to automate this step.
> It would just invisibly do what you were supposed to do anyway.

I believe in some rare cases this reinflation will fail. Such as when one makes
an inferior call which is normally OK but occasionally it may corrupt stack.

Or it could throw an exception in such case but I do not know if GDB codebase
is already exception-safe.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-04-03 20:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23342-4717@http.sourceware.org/bugzilla/>
2021-04-02 22:52 ` tromey at sourceware dot org
2021-04-03  5:54 ` tromey at sourceware dot org
2021-04-03 15:50 ` tromey at sourceware dot org
2021-04-03 19:36 ` simark at simark dot ca
2021-04-03 20:20 ` tromey at sourceware dot org
2021-04-03 20:31 ` jan.kratochvil at redhat dot com
2021-04-03 20:39 ` tromey at sourceware dot org
2021-04-03 20:42 ` tromey at sourceware dot org
2021-04-03 20:49 ` jan.kratochvil at redhat dot com [this message]
2022-10-17 22:30 ` tromey at sourceware 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-23342-4717-RTC2OP3OvU@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).