From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>, Manoj Iyer <manjo@austin.ibm.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb.server testcases (resend)
Date: Sun, 22 May 2005 21:01:00 -0000 [thread overview]
Message-ID: <20050522171656.GA1384@nevyn.them.org> (raw)
In-Reply-To: <20050522171520.GA1223@nevyn.them.org>
On Sun, May 22, 2005 at 01:15:20PM -0400, Daniel Jacobowitz wrote:
> Yes, this will not work. The correct way to handle this is to wait
> until I have implemented the available target features proposal I've
> posted on gdb@, and then I can make gdbserver inform GDB that 64-bit
> registers are available so that it will expect them.
>
> This will require some surgery in GDB, I'm sure. The way MIPS
> implements this is not very reliable.
I should add: it won't work for LinuxThreads libthread_db-based
debugging either. I don't know if it will work for NPTL, but I hope
that it will. Some changes were made to libthread_db to support this.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-22 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 14:46 Wu Zhou
2005-05-19 17:52 ` Manoj Iyer
2005-05-28 22:51 ` [commit] gdbserver for powerpc64-linux Daniel Jacobowitz
2005-05-22 20:40 ` [RFC] gdb.server testcases (resend) Daniel Jacobowitz
2005-05-22 21:01 ` Daniel Jacobowitz [this message]
2005-05-23 11:21 ` Wu Zhou
2005-05-23 18:26 ` Daniel Jacobowitz
2005-05-24 4:17 ` Wu Zhou
2005-05-24 8:29 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2005-05-17 2:38 Manoj Iyer
2005-05-17 19:02 ` Manoj Iyer
2005-05-18 1:45 ` Daniel Jacobowitz
2005-05-18 9:52 ` Manoj Iyer
2005-05-18 16:01 ` Daniel Jacobowitz
2005-05-18 16:29 ` Manoj Iyer
2005-05-18 18:08 ` Daniel Jacobowitz
2005-05-18 22:08 ` Manoj Iyer
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=20050522171656.GA1384@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=manjo@austin.ibm.com \
--cc=woodzltc@cn.ibm.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