multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi <peter_tkchoi@yahoo.com>]

Hi,

  I compiled GDB6.3 host=i686-linux,
target=i386-linux.

  On the i386 target, run the compiled gdbserver, and
then break the middle of my test program. However, I
can only view 1 thread (main), all other thread cannot
be seen.

1. ldd gdbserver:
	libthread_db.so.1 => /lib/tls/libthread_db.so.1
(0x00996000)
	libc.so.6 => /lib/tls/libc.so.6 (0x0085b000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00843000)

  It seems that libthread_db.so has been linked to
gdbserver.

But...
2. after breaking in the middle of my test program, I
examine the /proc/PID/maps:

00843000-00858000 r-xp 00000000 03:02 755706    
/lib/ld-2.3.2.so
00858000-00859000 rw-p 00015000 03:02 755706    
/lib/ld-2.3.2.so
0085b000-0098e000 r-xp 00000000 03:02 985716    
/lib/tls/libc-2.3.2.so
0098e000-00991000 rw-p 00132000 03:02 985716    
/lib/tls/libc-2.3.2.so
00991000-00994000 rw-p 00000000 00:00 0
00ae5000-00af2000 r-xp 00000000 03:02 985718    
/lib/tls/libpthread-0.60.so
00af2000-00af3000 rw-p 0000c000 03:02 985718    
/lib/tls/libpthread-0.60.so
00af3000-00af5000 rw-p 00000000 00:00 0
00c58000-00c5f000 r-xp 00000000 03:02 755708    
/lib/libgcc_s-3.3.2-20031023.so.1
00c5f000-00c60000 rw-p 00006000 03:02 755708    
/lib/libgcc_s-3.3.2-20031023.so.1
08048000-08049000 r-xp 00000000 03:05 1558879   
/home/pchoi/dev/test
08049000-0804a000 rw-p 00000000 03:05 1558879   
/home/pchoi/dev/test
099c9000-099ea000 rw-p 00000000 00:00 0
bc37f000-bc380000 ---p 00000000 00:00 0
bc380000-bcd80000 rw-p 00001000 00:00 0
bcd80000-bcd81000 ---p 00000000 00:00 0
bcd81000-bd781000 rw-p 00001000 00:00 0
bd781000-bd782000 ---p 00000000 00:00 0
bd782000-be182000 rw-p 00001000 00:00 0
be182000-be183000 ---p 00000000 00:00 0
be183000-beb84000 rw-p 00001000 00:00 0
beb84000-beb85000 ---p 00000000 00:00 0
beb85000-bf586000 rw-p 00001000 00:00 0
bfe5b000-c0000000 rw-p fff03000 00:00 0

   It seems that libthread_db.so has not been invoked.

3. I has tried "set debug remote 1" to examine the
remote protocol packets, but have no idea how shall
the expected packet look like??

  Please advise. Thank you for your attention.

Regards.
Peter Choi



		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs