From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] PTRACE_*REGS and x86-64-linux support for gdbserver
Date: Tue, 26 Feb 2002 23:08:00 -0000 [thread overview]
Message-ID: <20020227020808.A21701@nevyn.them.org> (raw)
In-Reply-To: <3C7C8196.2030005@cygnus.com>
On Wed, Feb 27, 2002 at 01:49:58AM -0500, Andrew Cagney wrote:
> Yes, ok.
Thanks, committed.
> I noticed, in an earlier patch you create a new ``..._linux'' .dat file.
> That addresses the only concern I had - were some of these register
> format files GNU/Linux specific. If they were, you were renaming them.
They weren't; at the time I made them, we had the glorious state of
affairs where none of the Linux targets had unique register mappings.
At least, I still believe that. orig_eax came along later and put the
lie to that... I still feel like there should be a better solution;
but that will require some thinking about the remote protocol, and can
wait.
The new register file conveniently snuck in just under the 8.3 ARI
limit, too :)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-02-27 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 22:37 Daniel Jacobowitz
2002-02-26 22:50 ` Andrew Cagney
2002-02-26 23:08 ` Daniel Jacobowitz [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=20020227020808.A21701@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.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