Re: gdb debugging threads help

[Daniel Jacobowitz <drow@false.org>]

On Thu, Nov 17, 2005 at 06:36:10PM -0600, Teresa Rivas wrote:
> on the target:
> # gdbserver :5234 simple

Is gdbserver linked to libthread_db?  Check the build log, or check the
gdbserver binary.

> (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.

> (gdb) set solib-search-path /target/arm-linux/lib

You should not need to set that.

> (gdb) dir /target/arm-linux/lib

Or this.

> Source directories searched: /target/arm-linux/lib:$cdir:$cwd
> (gdb) set endian little
> The target is assumed to be little endian

Or this.

> (gdb) handle SIG32 nostop noprint pass
> Signal        Stop      Print   Pass to program Description
> SIG32         No        No      Yes             Real-time event 32

Don't do that; it never helps.

> (gdb) add-symbol-file simple
> add symbol table from file "simple" at
> (y or n) y
> Reading symbols
> from /home/trivas/dm320-appro/fs/examples/threads/simple...done.

Don't do this either.  Use "file simple", and do it before issuing the
"target remote" command.

> and if I try a info shared it says "No shared libraries loaded at this
> time"

Thread debugging will not work until this works.  It should show you
the list of libraries and say that they have symbols loaded (at main,
not when you first connect).

-- 
Daniel Jacobowitz
CodeSourcery, LLC