Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Remote Debugging Of Multithreaded Application on PPC 82xx
@ 2003-03-14 14:03 Frank.Christ
  2003-03-14 14:17 ` Daniel Jacobowitz
  0 siblings, 1 reply; 2+ messages in thread
From: Frank.Christ @ 2003-03-14 14:03 UTC (permalink / raw)
  To: gdb

I am trying to setup a remote debugging session, so that I can debug my
multithreaded
application running on PPC 82xx and use gdb on my Intel host (i686, SuSE 7.0).

I downloaded gdb version 5.3 and compiled gdb on the host (with target
powerpc-linux).
I also cross-compiled gdbserver (with option powerpc-linux).

I have /lib/libthread_db.so.1 on the 8xx
  have the target filesystem layout available on the host
  have solib-absolute-prefix set to point to the target libraries
(solib-absolute-prefix=/opt/elinos/cdk/ppc/82xx/libc6/powerpc-linux)

I can start the gdbserver on the target and gdb on the host and have a
connection by tcp/ip.
The application is multithreaded and uses the libpthread library. I can put
breakpoints in
every thread and break into my code. "info threads" gives all my threads and
everything
seems fine.

However:
I can step through the main thread, but I cannot step through all my other
threads. When
I try to step with next in a client thread I get the following message:

-------------------------------------
 (gdb) next

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 1024]
0x0feee8a4 in nanosleep () from
/opt/elinos/cdk/ppc/82xx/libc6/powerpc-linux/lib/libc.so.6
------------------------------------

Any hints what my be wrong with my configuration?

Thanks in advance,
Frank Christ






^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-03-14 14:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-14 14:03 Remote Debugging Of Multithreaded Application on PPC 82xx Frank.Christ
2003-03-14 14:17 ` Daniel Jacobowitz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox