From: "Linh Dang" <linhd@nortelnetworks.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb@sources.redhat.com
Subject: Re: NPTL on ppc
Date: Tue, 07 Dec 2004 14:33:00 -0000 [thread overview]
Message-ID: <wn5acsqmb4b.fsf@linhd-2.ca.nortel.com> (raw)
In-Reply-To: <jer7m33tfn.fsf@sykes.suse.de> (Andreas Schwab's message of "Tue, 07 Dec 2004 00:20:28 +0100")
Andreas Schwab <schwab@suse.de> wrote:
> Daniel Jacobowitz <drow@false.org> writes:
>
>> If so, I'm out of ideas; you will have to debug it yourself.
>
> NPTL debugging requires a functional implementation of ps_lgetregs,
> but gdbserver on ppc does not implement it.
dummy question:
ptrace(2) on linux-ppc doesn't support PTRACE_GETREGS, how does gdb
get registers from the inferior process? (the native gdb works fine
with NPTL, just gdbserver that has trouble.)
Thanx
--
Linh Dang
next prev parent reply other threads:[~2004-12-07 14:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 14:23 pthreads debug with gdbserver Vladimir Vorobyov
2004-11-19 14:42 ` Daniel Jacobowitz
2004-11-19 15:59 ` Vladimir Vorobyov
2004-11-20 10:01 ` Daniel Jacobowitz
2004-11-20 16:42 ` Vladimir Vorobyov
2004-11-20 16:57 ` Daniel Jacobowitz
2004-11-20 17:13 ` Andreas Schwab
2004-11-20 17:38 ` Vladimir Vorobyov
2004-12-06 18:41 ` NPTL on ppc (was: pthreads debug with gdbserver) Linh Dang
2004-12-06 18:45 ` Daniel Jacobowitz
2004-12-06 19:56 ` NPTL on ppc Linh Dang
2004-12-06 20:18 ` Daniel Jacobowitz
2004-12-06 22:41 ` Andreas Schwab
2004-12-06 23:20 ` Andreas Schwab
2004-12-07 14:33 ` Linh Dang [this message]
2004-12-07 14:56 ` Andreas Schwab
2004-12-06 22:04 ` Andreas Schwab
2004-11-22 14:07 ` pthreads debug with gdbserver Vladimir Vorobyov
2004-11-22 18:04 ` Daniel Jacobowitz
2004-11-23 19:33 ` Vladimir Vorobyov
2004-11-19 16:19 ` Andreas Schwab
2004-11-19 17:30 ` Vladimir Vorobyov
2004-11-20 1:31 ` Andreas Schwab
2004-11-20 1:32 ` Daniel Jacobowitz
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=wn5acsqmb4b.fsf@linhd-2.ca.nortel.com \
--to=linhd@nortelnetworks.com \
--cc=gdb@sources.redhat.com \
--cc=schwab@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).