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 20:42:00 -0000	[thread overview]
Message-ID: <40C8C7C2.5060100@gnu.org> (raw)
In-Reply-To: <20040610202337.GH561@tausq.org>

>>Can push_dummy_call set these space registers, and the generic pop dummy 
>>> frame code restore them?
> 
> 
> No. Unfortunately it's not possible to use the regular ttrace mechanism
> to set the pcsqh/pcsqt (aka iasq[0] and iasq[1]) registers.... bascially
> you need to execute a bit of code:
> 
> (assuming pcoqh (aka pc) is in r21 and pcsqh is in r22)
> ldsid (%r22), %r1
> mtsp %r1, %sr0
> be 0(%sr0, %r21)
> 
> this branches to (%r22, %r21), thereby setting the space register ...

Sigh (the relevant code will need comments explaining this).  Are you 
absolutely positively certain this is true (for both HP/UX 10.20 / 
11.xx)? :-)

Also that sequence in the call path, the return path, or both?

Having the dummy-code containing a non-trivial sequence of instructions 
opens up the problem of needing to be able to step through them.  Issues 
similar to the grief I've been going through with signal trampolines.

Andrew



  reply	other threads:[~2004-06-10 20:42 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
2004-06-10 20:23   ` Randolph Chung
2004-06-10 20:42     ` Andrew Cagney [this message]
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=40C8C7C2.5060100@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