* Strange "info threads" behaviour. (linux]
@ 2001-05-04 14:35 Fabrice Gautier
2001-05-06 9:39 ` Mark Kettenis
0 siblings, 1 reply; 2+ messages in thread
From: Fabrice Gautier @ 2001-05-04 14:35 UTC (permalink / raw)
To: gdb
Hi,
I'm using latest gdb snapshot to debug a program using libpthread.
I compiled gdb on a debian unstable box, adn debuging my programs works
fine. Info thread return correct informations.
But my goal is to use this progrma on a embdedd linux platform.
This platform uses a STPC CPU. It has a minimal filesystem, all libs and
binaries are directly copied from the debian box. Everything is the same
version than on the debian box. Kernels are both 2.4.3, but their config
are somewhat differents.
So when i run gdb on the STPC, when i type info threads i didn't get any
info. I didn't get an error neither. I just type "info threads", enter
and i get back to the gdb prompt..
How could this be explained?
Does some missing part of the system on the STPC platform could produce
this?
Thanks
--
Fabrice Gautier <gautier@email.enstfr>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Strange "info threads" behaviour. (linux]
2001-05-04 14:35 Strange "info threads" behaviour. (linux] Fabrice Gautier
@ 2001-05-06 9:39 ` Mark Kettenis
0 siblings, 0 replies; 2+ messages in thread
From: Mark Kettenis @ 2001-05-06 9:39 UTC (permalink / raw)
To: Fabrice Gautier; +Cc: gdb
Fabrice Gautier <gautier@email.enst.fr> writes:
Are you using a native GDB on your embedded platform? If so, it could
be be that /lib/libthread_db.so.1 is missing on your embedded system.
Otherwise, I don't think that debugging multi-threaded programs
remotely is possible at all.
Mark
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-05-06 9:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-05-04 14:35 Strange "info threads" behaviour. (linux] Fabrice Gautier
2001-05-06 9:39 ` Mark Kettenis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox