From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>
Subject: Re: [RFC] i386/amd64 biarch gdbserver
Date: Mon, 11 May 2009 17:50:00 -0000 [thread overview]
Message-ID: <200905111850.46214.pedro@codesourcery.com> (raw)
In-Reply-To: <20090509191225.404D984890@localhost>
On Saturday 09 May 2009 20:12:25, Doug Evans wrote:
> This patch implements biarch i386/amd64 gdbserver.
> I haven't done anything with xml target descriptions, but there
> are no regressions so it seems like a good stopping place.
Yeah, this came up on IRC, when I mentioned about gdbserver
multi-process, and debugging 32-bit and 64-bit inferiors
simultaneously. The x86 and amd64 register sets aren't compatible,
and, we've got a single target_gdbarch to represent the connection, so
this is a problem. But it's one we can solve on top of this.
> This patch also fixes a bug where current amd64 gdbserver
> doesn't handle xmm[8-15]. Testcase to follow later.
>
> Tested on
> - i386-linux
> - x86_64-linux with gcc -m64
> - x86_64-linux with gcc -m32 (and hacking site.exp to specify i386-linux)
> using --target_board=native-gdbserver
> [ref http://sourceware.org/gdb/wiki/Native_gdbserver_testing]
>
> Comments?
This looks good to me, but, I don't know how far can I stretch in
gdbserver approvals.
Small nit, you've added an `assert' call, but I think you should use `fatal'
instead -- there are no other references to `assert' in gdbserver whole.
> +/* Return non-zero if the target is 64-bit. */
> +
> +static void
> +x86_arch_setup (void)
Misplaced comment?
--
Pedro Alves
next prev parent reply other threads:[~2009-05-11 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 19:12 Doug Evans
2009-05-11 17:50 ` Pedro Alves [this message]
2009-05-11 19:16 ` Joel Brobecker
2009-05-11 21:18 ` Pedro Alves
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=200905111850.46214.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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