From: Randolph Chung <tausq@debian.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Don't unwind past entry point
Date: Wed, 10 Nov 2004 17:07:00 -0000 [thread overview]
Message-ID: <20041110170737.GI15714@tausq.org> (raw)
In-Reply-To: <41924990.9060504@gnu.org>
> Check eli for the doco.
ok, i'll wait for Eli :)
> The code change is ok (while your though though, can you do me a favour
> and move inside_entry_func to frame.c and make it static?).
will do.
> This is missing a testcase but for that I'll need to take a raincheck -
> we've almost but not quite got a setbacktrace testcase and it should be
> extended to include this. Can you watch for that.
mmm.. this might be a bit tricky, as at least the original problem
depended on a particular compiler optimization that might not always
happen. but i can write up a testcase using the example i posted and
just use that...
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2004-11-10 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 19:24 Randolph Chung
2004-11-10 17:03 ` Andrew Cagney
2004-11-10 17:07 ` Randolph Chung [this message]
2004-11-10 18:13 ` Paul Gilliam
2004-11-10 20:47 ` Eli Zaretskii
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=20041110170737.GI15714@tausq.org \
--to=tausq@debian.org \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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