From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>, davidm@hpl.hp.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: new gdb arch routine FRAME_UNCHANGED
Date: Mon, 13 May 2002 15:57:00 -0000 [thread overview]
Message-ID: <1020513225722.ZM616@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@cygnus.com> "Re: new gdb arch routine FRAME_UNCHANGED" (May 13, 6:46pm)
On May 13, 6:46pm, Andrew Cagney wrote:
> Also, code wants to determine which code is more INNER_THAN(). With two
> stacks, that starts to get really weird!
Yes. On IA-64, the meaning of INNER_THAN is different for the two stacks.
(I.e, the stacks grow in different directions.)
Kevin
next prev parent reply other threads:[~2002-05-13 22:57 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 [this message]
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
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=1020513225722.ZM616@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@cygnus.com \
--cc=davidm@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