From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: support libthread_db xregset functions
Date: Fri, 26 Mar 2004 03:08:00 -0000 [thread overview]
Message-ID: <20040326030845.GA30012@nevyn.them.org> (raw)
In-Reply-To: <4062FFA5.9040704@gnu.org>
On Thu, Mar 25, 2004 at 10:49:57AM -0500, Andrew Cagney wrote:
> Jim,
>
> + # See the definition of 'struct xregset_desc' in gregset.h.
> + v::XREGSET_DESC:struct xregset_desc
> *:xregset_desc:::::0::0:%p:current_gdbarch->xregset_desc
>
> Back in oct MarkK added "regset.h", while the write path is missing that
> is definitly the right way to go.
Yes, definitely. We need the write path to support things like cross
generate-core-file anyway.
I may rip out the indirection through thread-db for this particular
case after 6.1. It seems increasingly clear that using enough of
thread-db to support non-1:1 threading is no longer a useful feature.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-03-26 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 19:15 Jim Blandy
2004-03-25 15:49 ` Andrew Cagney
2004-03-26 3: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=20040326030845.GA30012@nevyn.them.org \
--to=drow@false.org \
--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