I need more information on what specific software causes this problem and
how to fix the problem where gdb is not able to identify pthreads. The
scenario is on a simple threaded application runs fine and debugs fine on a
recent red hat i686 system (specs below) but on very similar system w/ a
customized kernel with the exact same libraries, gdb returns nothing for
"info threads", and does not report new thread creation on start up, I also
get SIG32's on the non-working system. I'm convinced I have eliminated any
differences in gdb and libraries in use, and am looking for the specific
kernel source that has been patched.
This system works:
i686 linux 2.4.9-31
GNU gdb Red Hat Linux (5.1-1)
ldd gdb
libncurses.so.5 => /usr/lib/libncurses.so.5 (0x40018000)
libm.so.6 => /lib/i686/libm.so.6 (0x4006c000)
libdl.so.2 => /lib/libdl.so.2 (0x4008f000)
libc.so.6 => /lib/i686/libc.so.6 (0x40093000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
ldd simple-threaded-program
libpthread.so.0 => /lib/i686/libpthread.so.0 (0x4002b000)
libc.so.6 => /lib/i686/libc.so.6 (0x40040000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
The system with newer kernel sources (from kernel.org) does not:
i686 linux 2.4.10-custom (built from recent source from kernel.org)
GNU gdb Red Hat Linux (5.1-1)
The libs are the same as listed above.
Is there specific kernel source, or a red hat patch or configuration that
affects
gdb of threads?
Thanks,
-- Ralf Durkee
Independent Consultant
http://rd1.net
