From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] frame_id_unwind
Date: Wed, 31 Mar 2004 19:42:00 -0000 [thread overview]
Message-ID: <406B1F1C.7040100@gnu.org> (raw)
In-Reply-To: <4062EBF9.7040908@gnu.org>
> 2004-03-25 Andrew Cagney <cagney@redhat.com>
>
> * frame.h (frame_unwind_id): Declare.
> * frame.c (frame_unwind_id): New function.
> (get_prev_frame_1): New function.
> (frame_debug_got_null_frame): New function.
> (get_prev_frame): Use frame_debug_got_null_frame. Move unwind
> code proper to prev_frame, update description.
> * infrun.c (step_over_function): Use frame_unwind_id.
>
I've checked this in.
Per discussion, something to follow up is replacing get_prev_frame.
Andrew
prev parent reply other threads:[~2004-03-31 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 14:26 Andrew Cagney
2004-03-28 18:16 ` Jim Blandy
2004-03-28 22:31 ` Andrew Cagney
2004-03-29 6:47 ` Eli Zaretskii
2004-03-31 19:42 ` Andrew Cagney [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=406B1F1C.7040100@gnu.org \
--to=cagney@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