From: Linh Dang <linhd@nortelnetworks.com>
To: gdb@sources.redhat.com
Subject: NPTL on ppc (was: pthreads debug with gdbserver)
Date: Mon, 06 Dec 2004 18:41:00 -0000 [thread overview]
Message-ID: <wn5mzwrmgm5.fsf_-_@linhd-2.ca.nortel.com> (raw)
In-Reply-To: <20041120164209.GA15174@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> wrote:
>
> Take a look at the source code to gdbserver. Andreas, now I
> remember why I enabled thread_db support on a per-target basis -
> there are other support routines that have to be written.
Hi Daniel and Andreas,
Does gdbserver works with NPTL on ppc32? I use 6.3.50 and I keep
getting on the target side:
gdbserver 47.129.74.85:8888 p_greetings2
Process p_greetings2 created; pid = 288
Listening on port 8888
Remote debugging from host 47.129.74.85
error = 0
error = 0
Cannot find new threads: generic error
error = 0
Cannot find new threads: generic error
error = 0
Cannot find new threads: generic error
and on the host side:
target extended-remote 47.135.196.213:8888
Remote debugging using 47.135.196.213:8888
0x30011e28 in ?? ()
(gdb) b main
Breakpoint 1 at 0x1000080c
(gdb) info b
Num Type Disp Enb Address What
1 breakpoint keep y 0x1000080c <main+28>
(gdb) c
Continuing.
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Breakpoint 1, 0x1000080c in main ()
(gdb) info shared
From To Syms Read Shared Object Library
0x0ffd17e4 0x0ffdbd4c Yes /linux-tools-2.6/powerpc-linux/lib/libpthread.so.0
0x0fe9b060 0x0ff850a4 Yes /linux-tools-2.6/powerpc-linux/lib/libc.so.6
0x30001ee0 0x300155d0 Yes /linux-tools-2.6/powerpc-linux/lib/ld.so.1
(gdb)
Thanx
--
Linh Dang
next prev parent reply other threads:[~2004-12-06 18:41 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 ` Linh Dang [this message]
2004-12-06 18:45 ` NPTL on ppc (was: pthreads debug with gdbserver) 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
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=wn5mzwrmgm5.fsf_-_@linhd-2.ca.nortel.com \
--to=linhd@nortelnetworks.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