From: Daniel Jacobowitz <drow@mvista.com>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver ps_lgetregs implementation for nptl
Date: Fri, 12 Dec 2003 18:18:00 -0000 [thread overview]
Message-ID: <20031212181811.GA22730@nevyn.them.org> (raw)
In-Reply-To: <200312122036.57453.amitkale@emsyssoft.com>
On Fri, Dec 12, 2003 at 08:36:57PM +0530, Amit S. Kale wrote:
> Implementing the commented out code was trivial for i386 because it already
> has register sets. I implemented all ps_*getregs functions.
>
> A change was needed in gdb. I had to add support for qSymbol in
> remote.c:remote_wait. This was needed for a symbol query from nptl.
>
> I am pasting below code from ps_lsetregs modified by me. I removed creation of
> a register cache. before fetch_registers and fill_function. Is this the right
> way of doing it?
<snip>
Before I look at your code, do you have or plan to have an FSF
copyright assignment for GDB?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-12 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 9:43 Amit S. Kale
2003-12-11 14:14 ` Daniel Jacobowitz
2003-12-12 15:07 ` Amit S. Kale
2003-12-12 18:18 ` Daniel Jacobowitz [this message]
2003-12-13 18:39 ` Jim Blandy
2003-12-15 6:08 ` Amit S. Kale
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=20031212181811.GA22730@nevyn.them.org \
--to=drow@mvista.com \
--cc=amitkale@emsyssoft.com \
--cc=gdb@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