From: Mark Wielaard <mark@klomp.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: [patch] Don't crash on stepping "bad frame"
Date: Sun, 02 Mar 2008 12:34:00 -0000 [thread overview]
Message-ID: <1204460137.8622.4.camel@localhost.localdomain> (raw)
In-Reply-To: <47C82C87.4090600@redhat.com>
Hi Andrew,
On Fri, 2008-02-29 at 11:02 -0500, Andrew Cagney wrote:
> Interesting work-around; I'll add some comments to explain exactly
> where/when this senario occures. And where/when it doesn't. For
> instance a step-out through a sigalt stack, whith a bad unwind, will
> make the wrong decision.
Yes, please do add such documentation if you can. That would be very
valuable.
Note that there isn't any "good" decision really in the case of bad
unwind info where getOuterFrame() has to return null. Currently we try
to get the user back to "known territory", but we could also just drop
the user at the "bad address" and let them sort it out themselves.
Neither is really attractive of course.
Cheers,
Mark
prev parent reply other threads:[~2008-03-02 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 15:14 Mark Wielaard
2008-02-29 16:03 ` Andrew Cagney
2008-03-02 12:34 ` Mark Wielaard [this message]
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=1204460137.8622.4.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=cagney@redhat.com \
--cc=frysk@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).