Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: frame id enhancement
Date: Tue, 14 Oct 2003 21:59:00 -0000	[thread overview]
Message-ID: <3F8C71D9.7010507@redhat.com> (raw)
In-Reply-To: <3F81DB50.6020202@redhat.com>

Ping.

J. Johnston wrote:
> The following patch enhances the frame id support to allow an architecture
> to set a special address for the frame.  This enables architectures such 
> as the
> ia64 (which has a 2nd stack) to properly mark distinct frames.  I added a
> new routine that builds frame ids that has a special address parameter.  
> The
> current frame_id_build() has been changed to call the new routine with a 
> default
> special address of 0.  This means that existing calls to 
> frame_id_build() require
> no changes.
> 
> Ok to commit to mainline?
> 
> -- Jeff J.
> 
> 2003-10-06  Jeff Johnston  <jjohnstn@redhat.com>
> 
>     * frame.h (struct frame_id): Add new field: special_addr.
>     (frame_id_build_special): New prototype.
>     * frame.c (frame_id_build_special): New function.
>     (frame_id_build): Change to call frame_id_build_special().
>     (frame_id_eq): Change to also test special_addr field.


  reply	other threads:[~2003-10-14 21:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 21:15 J. Johnston
2003-10-14 21:59 ` J. Johnston [this message]
2003-10-15 21:09 ` Andrew Cagney
2003-10-15 23:12   ` J. Johnston
2003-10-16 16:09     ` Andrew Cagney
2003-10-16 19:06       ` J. Johnston
2003-10-16 21:06         ` Andrew Cagney
2003-10-16 21:49           ` J. Johnston
2003-10-16 23:32             ` J. Johnston
2003-10-17 13:30               ` Andrew Cagney
2003-10-17 16:32                 ` J. Johnston
2003-10-17 18:11             ` Kevin Buettner
2003-10-17 19:34               ` J. Johnston

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=3F8C71D9.7010507@redhat.com \
    --to=jjohnstn@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