Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Try to get dummy calls working on hpux again
Date: Thu, 10 Jun 2004 19:27:00 -0000	[thread overview]
Message-ID: <40C8B609.5000704@gnu.org> (raw)
In-Reply-To: <20040610061234.GF561@tausq.org>

> A lot of the original code to handle dummy calls were ripped out of
> hppa-tdep.c in March.  This patch brings back some of that logic so that
> we can start to make it work again on hpux.
> 
> The PA has "space registers" (like segment registers on x86, sort of).
> We don't use this for hppa-linux, so simply using push_dummy_call was
> enough. HPUX uses it though....
> 
> Because the caller and callee may be in different spaces, we need to go
> through some hoops to set/reset the space registers across calls. The
> original code had many special cases to handle multiple targets, and
> multiple function types. This only brings back some of that logic, and 
> it only works for 32-bit SOM at the moment. My plan is to try to fix 
> this incrementally rather than get it "perfect" on the first try....

Can push_dummy_call set these space registers, and the generic pop dummy 
frame code restore them?

> this fixes calling shared library functions from inside gdb, so it
> fixes quite a few test failures, but there are many more! :(
> 
> comments? ok to check in? 

Andrew



  reply	other threads:[~2004-06-10 19:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10  6:12 Randolph Chung
2004-06-10 19:27 ` Andrew Cagney [this message]
2004-06-10 20:23   ` Randolph Chung
2004-06-10 20:42     ` Andrew Cagney
2004-06-10 22:12       ` Randolph Chung
2004-06-11 15:25         ` Andrew Cagney
2004-06-11 16:12           ` Randolph Chung
2004-06-11 17:30             ` Andrew Cagney
2004-07-11  6:53               ` Randolph Chung
2004-07-14 16:54                 ` 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=40C8B609.5000704@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /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