The GDB I have (w/RH 5.1) doesn't support Linux's pthreads implementation.
Anyone know of any patches or other de*s that do?
George T. Talbot
Michael D. Hirsch Work: (404) 727-7940
Emory University, Atlanta, GA 30322 FAX: (404) 727-5611
Public key for encrypted mail available upon request (or finger
> The Open Group has a set of patches for gdb to support debugging
> threads. URL, anybody?
Does anybody have any experiences with this patch?
//|| ||\\ http://www.veryComputer.com/~awd/
// ||ndreas |//ischinger PGP-Key by finger.
Forschungszentrum Informatik (FZI)
`Anyone who says you can have a lot of widely dispersed people hack
away on a complicated piece of code and avoid total anarchy has never
managed a software project.' - Andy Tanenbaum in 1992 on comp.os.minix
I'm 3.0-RELEASE user.
I made some test programs which uses pthread library.
It worked very well.
After getting successful results, I tried to use GDB to get detailed
thread specific information.
But I could not see created threads in GDB.
The GDB command 'info threads' just print nothing as if it do not have
No thread related commands work.
GDB in 3.0-RELEASE does not support threads?
Or is there any other ways to let GDB know threads?
Another question, when I link pthread application with '-lc_r' option ,
linker complains like this.
gcc -o mytest a.o b.o c.o -lc_r
/usr/lib/libc.so: warning: this program uses gets(), which is unsafe.
/usr/lib/libc.so: WARNING! setkey(3) not present in the system!
/usr/lib/libc.so: WARNING! des_setkey(3) not present in the system!
/usr/lib/libc.so: WARNING! encrypt(3) not present in the system!
/usr/lib/libc.so: WARNING! des_cipher(3) not present in the system!
/usr/lib/libc.so: warning: this program uses f_prealloc(), which is
When I use '-pthread' option instead of '-lc_r', the linker says
gcc -pthread -o mytest a.o b.o c.o
Is there any fundamental difference between '-lc_r' and '-pthread'