Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Thu, 11 Dec 2003 14:14:00 -0000	[thread overview]
Message-ID: <20031211141429.GB26315@nevyn.them.org> (raw)
In-Reply-To: <200312111513.23927.amitkale@emsyssoft.com>

On Thu, Dec 11, 2003 at 03:13:23PM +0530, Amit S. Kale wrote:
> Hi,
> 
> I am trying to debug nptl programs using gdbserver on x86 platform. First 
> problem I found was missing ps_get_thread_area, which was easy to copy from 
> the implementation in gdb. Then error return from ps_lgetregs caused a 
> problem. ps_lgetregs has come code, though it's commented out. Any ideas on 
> completing that code?

I've been meaning to make it work with NPTL and not found the time...
However, it will take more than making it load to make it work.  I
expect that it will also require an extension to the remote protocol to
query the thread base address.

ps_get_thread_area in LinuxThreads was only called by functions that
gdbserver did not use.  If it's necessary for LinuxThreads - it appears
to be - then you'll have to supply a working version.  This will
require describing register sets in gdbserver, which it already can do
on some platforms (see the code that uses PTRACE_GETREGS).

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-12-11 14:14 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 [this message]
2003-12-12 15:07   ` Amit S. Kale
2003-12-12 18:18     ` Daniel Jacobowitz
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=20031211141429.GB26315@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