From: Jim Blandy <jimb@red-bean.com>
To: teresa.rivas@cadenux.com
Cc: gdb@sources.redhat.com
Subject: Re: gdb debugging threads help
Date: Fri, 18 Nov 2005 01:19:00 -0000 [thread overview]
Message-ID: <8f2776cb0511171719k2ff35effqda392d272f97ab7@mail.gmail.com> (raw)
In-Reply-To: <1132274170.32154.20.camel@localhost.localdomain>
On 11/17/05, Teresa Rivas <teresa.rivas@cadenux.com> wrote:
> I see there is a thread-db.o target on the gdb/Makefile file but I can't
> configure gdb so it execute this thread-db.o target which I believe add
> the gdb debbug thread support.
I haven't used gdbserver much, but I can at least tell you not to
worry about thread-db.o. That's not appropriate for cross-debugging
configurations; it's only used for native debugging. That file acts
as the interface between GDB and the libthread_db.so provided by the
operating system; when cross-debugging, it's gdbserver that needs to
link against the libthread_db.so, not GDB.
next prev parent reply other threads:[~2005-11-18 1:19 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 [this message]
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
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=8f2776cb0511171719k2ff35effqda392d272f97ab7@mail.gmail.com \
--to=jimb@red-bean.com \
--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