From: Daniel Jacobowitz <drow@false.org>
To: Teresa Rivas <teresa.rivas@cadenux.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb debugging threads help
Date: Fri, 18 Nov 2005 15:28:00 -0000 [thread overview]
Message-ID: <20051118152848.GC9100@nevyn.them.org> (raw)
In-Reply-To: <1132324238.32154.30.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2005-11-18 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 0:35 Teresa Rivas
2005-11-18 1:19 ` Jim Blandy
2005-11-18 2:36 ` Daniel Jacobowitz
2005-11-18 14:30 ` Teresa Rivas
2005-11-18 14:38 ` Teresa Rivas
2005-11-18 15:28 ` Daniel Jacobowitz [this message]
2005-11-18 16:49 ` Teresa Rivas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051118152848.GC9100@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=teresa.rivas@cadenux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox