From: "Eli Zaretskii" <eliz@elta.co.il>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com, kettenis@chello.nl
Subject: Re: [patch rfc] push_dummy_call return a frame ID; eliminate need for read_fp
Date: Wed, 23 Apr 2003 14:37:00 -0000 [thread overview]
Message-ID: <2927-Wed23Apr2003123434+0300-eliz@elta.co.il> (raw)
In-Reply-To: <3EA5C113.7080906@redhat.com> (message from Andrew Cagney on Tue, 22 Apr 2003 18:24:19 -0400)
> Date: Tue, 22 Apr 2003 18:24:19 -0400
> From: Andrew Cagney <ac131313@redhat.com>
>
> This patch modifies the architecture method push_dummy_call() so that it
> returns a frame ID, and not just a stack pointer. That frame ID is then
> used:
Okay for the manual patch.
next prev parent reply other threads:[~2003-04-23 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 22:24 Andrew Cagney
2003-04-23 14:37 ` Eli Zaretskii [this message]
2003-04-23 18:48 ` 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=2927-Wed23Apr2003123434+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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