From: Andreas Schwab <schwab@suse.de>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] infcall.c cleanup - explict bp_addr variable
Date: Fri, 27 Jun 2003 23:05:00 -0000 [thread overview]
Message-ID: <je7k77m89c.fsf@sykes.suse.de> (raw)
In-Reply-To: <3EFCBF6F.2050805@redhat.com> (Andrew Cagney's message of "Fri, 27 Jun 2003 18:04:31 -0400")
Andrew Cagney <ac131313@redhat.com> writes:
|> Does, instead, a s/push_arguments/push_dummy_call/ and move the above code
|> to push_dummy_call (PC -> FUNC_ADDR, CALL_DUMMY_ADDRESS -> BP_ADDR) work?
Yes, that seems to work. I'll prepare a patch that also replaces the
deprecated read/write_register calls with the regcache functions.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-06-27 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 19:12 Andrew Cagney
2003-06-27 21:00 ` Andreas Schwab
2003-06-27 22:04 ` Andrew Cagney
2003-06-27 23:05 ` Andreas Schwab [this message]
2003-07-01 17:44 ` Andreas Schwab
2003-07-01 21:35 ` Kevin Buettner
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=je7k77m89c.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ac131313@redhat.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