From: Andrew Cagney <ac131313@cygnus.com>
To: "Peter.Schauer" <Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE>
Cc: gdb@sources.redhat.com
Subject: Re: Switch ARM, SPARC and i386 to generic dummy frames (PC_IN_CALL_DUMMY)?
Date: Mon, 15 Apr 2002 06:42:00 -0000 [thread overview]
Message-ID: <3CBAD8D5.4030605@cygnus.com> (raw)
In-Reply-To: <200204150751.JAA01272@reisser.regent.e-technik.tu-muenchen.de>
> AFAIK, generic dummy frames work only with the AT_ENTRY mechanism.
>
> But for 32 bit SPARC ABI we need ON_STACK, see
> http://sourceware.cygnus.com/ml/gdb/1999-q4/msg00064.html
> http://sources.redhat.com/ml/gdb-patches/2000-05/msg00041.html
> for an explanation.
>
> I am afraid that we have to extend the generic dummy frame code to allow
> ON_STACK, i
I've this feeling that I might have just (accidently!) done this. For
sparc, the problem may be more the register window gunk.
Andrew
prev parent reply other threads:[~2002-04-15 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-14 7:51 Andrew Cagney
2002-04-14 8:18 ` Daniel Jacobowitz
2002-04-14 8:33 ` Andrew Cagney
2002-04-14 8:53 ` Daniel Jacobowitz
2002-04-14 9:40 ` Andrew Cagney
2002-04-14 10:17 ` Daniel Jacobowitz
2002-04-15 0:51 ` Peter.Schauer
2002-04-15 6: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=3CBAD8D5.4030605@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE \
--cc=gdb@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