From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add a sentinel frame
Date: Mon, 27 Jan 2003 21:42:00 -0000 [thread overview]
Message-ID: <3E35A7D5.5080504@redhat.com> (raw)
In-Reply-To: <3E305670.3020700@redhat.com>
I've checked this in.
> 2003-01-23 Andrew Cagney <ac131313@redhat.com>
>
> * sentinel-frame.h, sentinel-frame.c: New files.
> * Makefile.in (frame.o): Update dependencies.
> (SFILES): Add sentinel-frame.c.
> (sentinel_frame_h): Define.
> (COMMON_OBS): Add sentinel-frame.o.
> (sentinel-frame.o): Specify dependencies.
> * frame.c: Include "sentinel-frame.h".
> (frame_register_unwind): Rewrite assuming that there is always a a
> ->next frame.
> (frame_register, generic_unwind_get_saved_register): Ditto.
> (frame_read_unsigned_register, frame_read_signed_register): Ditto.
> (create_sentinel_frame, unwind_to_current_frame): New functions.
> (get_current_frame): Rewrite using create_sentinel_frame and
> unwind_to_current_frame. When possible, always create a frame.
> (create_new_frame): Set next to the sentinel frame.
> (get_next_frame): Rewrite. Don't go below the level 0 frame.
> (deprecated_update_frame_pc_hack): Update the next frame's PC and
> ID cache when necessary.
> (frame_saved_regs_id_unwind): Use frame_relative_level.
> (deprecated_generic_get_saved_register): Use frame_relative_level,
> get_frame_saved_regs, get_frame_pc, get_frame_base and
> get_next_frame.
> (frame_saved_regs_register_unwind): Use get_frame_saved_regs and
> frame_register.
now back to kevin's question.
Andrew
next prev parent reply other threads:[~2003-01-27 21:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 20:54 Andrew Cagney
2003-01-27 21:42 ` Andrew Cagney [this message]
2003-02-10 23:36 ` Michal Ludvig
2003-02-11 16:48 ` Andrew Cagney
2003-02-18 11:21 ` Michal Ludvig
2003-02-19 13:27 ` Andrew Cagney
2003-02-19 14:04 ` Daniel Jacobowitz
2003-02-19 16:46 ` Andrew Cagney
2003-02-19 16:56 ` Daniel Jacobowitz
2003-02-19 17:11 ` Andrew Cagney
2003-02-19 17:17 ` Daniel Jacobowitz
2003-02-19 17:46 ` Andrew Cagney
2003-02-19 17:56 ` Daniel Jacobowitz
2003-02-19 18:36 ` Andrew Cagney
2003-02-19 18:52 ` Daniel Jacobowitz
2003-02-19 20:22 ` Andrew Cagney
2003-02-19 20:39 ` Daniel Jacobowitz
2003-02-19 21:21 ` Andrew Cagney
2003-02-20 19:32 ` Daniel Jacobowitz
2003-02-19 21:45 ` Andrew Cagney
2003-02-20 19:32 ` Daniel Jacobowitz
2003-02-25 16:24 ` Michal Ludvig
2003-02-25 19:43 ` Andrew Cagney
2003-02-25 21:00 ` Michal Ludvig
2003-02-25 21:12 ` Andrew Cagney
2003-02-26 8:04 ` Michal Ludvig
2003-02-27 18:27 ` Andrew Cagney
2003-02-28 13:02 ` Michal Ludvig
2003-02-28 15:48 ` Andrew Cagney
2003-03-05 17:38 ` Michal Ludvig
2003-03-05 18:25 ` Andrew Cagney
2003-03-06 16:00 ` Michal Ludvig
2003-03-06 20:13 ` Andrew Cagney
2003-03-06 22:42 ` [RFA] Dummy frames on x86-64 Michal Ludvig
2003-03-07 14:50 ` Andrew Cagney
2003-02-25 22:41 ` [patch/rfc] Add a sentinel frame Andrew Cagney
2003-02-25 21:21 Michael Elizabeth Chastain
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=3E35A7D5.5080504@redhat.com \
--to=ac131313@redhat.com \
--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