From: Andrew Cagney <ac131313@ges.redhat.com>
To: davidm@hpl.hp.com
Cc: gdb-patches@sources.redhat.com, davidm@napali.hpl.hp.com
Subject: Re: new gdb arch routine FRAME_UNCHANGED
Date: Wed, 26 Jun 2002 20:26:00 -0000 [thread overview]
Message-ID: <3D1A85F4.9000706@ges.redhat.com> (raw)
In-Reply-To: <200205110023.g4B0NVCF004832@napali.hpl.hp.com>
> The patch below defines a new gdbarch routine called FRAME_UNCHANGED.
> This is needed for gdb/ia64 because the ia64 architecture has two
> separate stack pointers (one for memory stack and one for register stack).
> Because of the two stacks, it's not possible to look just at the frame
> pointer and PC to determine whether a frame changed.
>
> If the patch looks OK, I'd appreciate if someone could apply it.
>
> Note: the patch below doesn't include the ia64 version of
> FRAME_UNCHANGED. It is part of a larger update to add unwind library
> support to gdb/ia64 and I'll submit that separately. So, for now, the
> patch is effectively a no-op for all platforms.
>
> Also, it will be necessary to re-generate gdbarch.[ch] after applying
> the patch.
Just to follow this up. The frame_id code has been committed. I think
this has the potential of affecting the way you did your patch. For
instance, it could compare frame_id's for either sameness or more
inner_than.
Andrew
prev parent reply other threads:[~2002-06-27 3:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 17:23 David Mosberger
2002-05-10 18:04 ` Andrew Cagney
2002-05-10 19:05 ` David Mosberger
2002-05-11 20:52 ` Andrew Cagney
2002-05-13 14:15 ` David Mosberger
2002-05-13 15:46 ` Andrew Cagney
2002-05-13 15:57 ` Kevin Buettner
2002-05-13 16:14 ` Andrew Cagney
2002-05-13 19:43 ` David Mosberger
2002-05-13 19:57 ` Andrew Cagney
2002-05-13 20:33 ` David Mosberger
2002-06-26 20:26 ` 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=3D1A85F4.9000706@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.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