Re: gdb debugging threads help

[Daniel Jacobowitz <drow at false dot org>]

On Fri, Nov 18, 2005 at 08:30:37AM -0600, Teresa Rivas wrote:
> Which command can I use to see if it is linked against the correct
> thread_db library?? I use a nm -D gdbserver but all I see are the
> symbols from the dynamic libraries not the libraries.

"ldd" on your target.

> .....
> 0000eeec T target_signal_to_name
> 0000ee90 T target_signal_to_string
>          U tcgetattr
>          U tcsetattr
>          U tcsetpgrp
>          U td_symbol_list
>          U td_ta_event_addr
>          U td_ta_event_getmsg
>          U td_ta_new
>          U td_ta_set_event
>          U td_ta_thr_iter
>          U td_thr_event_enable
>          U td_thr_get_info
> 0001f42c D the_low_target
> 00020784 B the_target
> 00014664 T thread_db_init
> 00020690 B thread_from_wait

Looks good.

> (gdb) set solib-absolute-prefix /lib
> (gdb) file simple

No, /target/arm-linux.

The _full path_ to libraries will be appended to this prefix:

> > > (gdb) set solib-absolute-prefix /target/arm-linux/lib
> > 
> > That's probably not right.  The paths below solib-absolute-prefix
> > should match the target filesystem.  So if solib-absolute-prefix
> > is "/target/arm-linux", then the target /lib/ld-linux.so.2 should be in
> > /target/arm-linux/lib/ld-linux.so.2.


-- 
Daniel Jacobowitz
CodeSourcery, LLC