RE: gdbserver multithreaded debugging problem

[nak26 <nak26@drexel.edu>]

>===== Original Message From cerickson@mvista.com =====
>Nik,
>The files you need are in the target/lib directory
>
>libthread_db.so.1  link to libthread_db-1.0.so
>libthread_db-1.0.so
>
>and the target/usr/lib directory
>
>libthread_bd.a
>libthread_db.so  link to ../../lib/libthread_db.so.1
>libthread_db_p.a
>
>Then things should just be AOK. Now if you stripped your executables
>that are running on your target then you have another problem. So
>be advised that while in debug do not strip any threaded programs.
>
>Cal

Cal:

Sorry to be bugging you again, but I still haven't had success resolving the 
issue. I have the links set up as you perscribed, and my lib path includes 
/usr/lib (I also tried it including both /usr/lib and /lib in this order and 
vice versa) but I'm still seeing the SIG32  messages.

----------------------------------------------------------
Here is my setup:
------------------------------------------------------------------------------
-------
lab@(none):/usr/lib$ ls -l | grep libthread
-rwxr-xr-x    1 root     root        95174 Mar 21 05:19 libthread.so
-rw-r--r--    1 root     root      2197690 Mar 21 04:06 libthread_db.a
lrwxrwxrwx    1 root     root           27 Jun 24 13:36 libthread_db.so -> 
../../lib/libthread_db.so.1
-rwxr-xr-x    1 root     root        25911 Mar 21 07:33 libthread_db.so.1.0.20
-rw-r--r--    1 root     root      2199126 Mar 21 04:06 libthread_db_p.a
-rwxr-xr-x    1 root     root       301667 Mar 21 05:20 libthreaddbg.so
lab@(none):/usr/lib$

lab@(none):/lib$ ls -l | grep libthread
-rw-r--r--    1 root     root       935480 Mar 21 04:06 libthread_db-1.0.so
lrwxrwxrwx    1 root     root           19 May  2 16:00 libthread_db.so.1 -> 
libthread_db-1.0.so
lab@(none):/lib$

lab@(none):~$ env | grep LD_LIB
LD_LIBRARY_PATH=/usr/lib:/lib:/opt/intel/mkl/lib/32
lab@(none):~$

--------------------------------------------------------------------

Per Daniel's suggestion I looked at the config.log, and multithreading seems 
to be set up correctly prior to the build.

I guess I can try debugging a multithreaded toy example, or hopefully you'll 
see something else that I'm doing wrong.

Thanks,
Nik