From: Frank Chen <frankxchen@yahoo.com>
To: gdb@sources.redhat.com
Subject: gdbserver couldn't find thread library
Date: Mon, 20 Feb 2006 05:07:00 -0000 [thread overview]
Message-ID: <20060220031628.35250.qmail@web34705.mail.mud.yahoo.com> (raw)
I am debugging a multi-threaded program using
gdbserver. The function call to td_ta_new in
thread_db_init() (in thread_db.c) returns
TD_NOLIBTHREAD. And the program does not run properly
afterwards.
However, when I debug the same program locally using
gdb, it works fine. The gdb displays the following
message during start up.
Using host libthread_db library
"/lib/tls/libthread_db.so.1"
Since this is a UI program, running gdb locally
doesn't work. I would like to use the gdbserver. It
seems that I need to point gdbserver to the above
location for the thread library. Could someone tell me
how to do that?
Thanks,
Frank
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next reply other threads:[~2006-02-20 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 5:07 Frank Chen [this message]
2006-02-20 5:49 ` Daniel Jacobowitz
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=20060220031628.35250.qmail@web34705.mail.mud.yahoo.com \
--to=frankxchen@yahoo.com \
--cc=gdb@sources.redhat.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