From: "Mudeem Siddiqui" <mudeem@quartics.com>
To: "Andreas Schwab" <schwab@suse.de>
Cc: "Michael Snyder" <msnyder@specifix.com>, <gdb@sourceware.org>
Subject: RE: debugging multi threaded application
Date: Mon, 12 May 2008 18:44:00 -0000 [thread overview]
Message-ID: <87A697E50899F541B77272C331CEB744016ED5FA@exchange.Q-DOMAIN> (raw)
In-Reply-To: <je1w4ad2ot.fsf@sykes.suse.de>
Hi Andreas,
Actually the tool chain was already compiled and I wasn't involved in it. Is there a way to check if uclibc was compiled with debugable thread support.
Regards
Mudeem
-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf Of Andreas Schwab
Sent: Saturday, May 10, 2008 12:44 AM
To: Mudeem Siddiqui
Cc: Michael Snyder; gdb@sourceware.org
Subject: Re: debugging multi threaded application
"Mudeem Siddiqui" <mudeem@quartics.com> writes:
> In my lib directory, I do have libthread_db but with slightly
> different name i.e libthread_db.so.0 and libthread_db-0.9.21.so.
> Attached Is config.log for the reference. What can I do to get this
> thing working :)
How did you set up the cross tools? You are missing the link from libthread_db.so to one of these files. The linker looks for libthread_db.so and libthread_db.a, but no other file.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
prev parent reply other threads:[~2008-05-12 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 1:16 Mudeem Siddiqui
2008-05-08 2:22 ` Daniel Jacobowitz
2008-05-08 18:46 ` Michael Snyder
2008-05-09 20:05 ` Mudeem Siddiqui
2008-05-10 1:45 ` Mudeem Siddiqui
2008-05-10 7:43 ` Andreas Schwab
2008-05-12 18:44 ` Mudeem Siddiqui [this message]
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=87A697E50899F541B77272C331CEB744016ED5FA@exchange.Q-DOMAIN \
--to=mudeem@quartics.com \
--cc=gdb@sourceware.org \
--cc=msnyder@specifix.com \
--cc=schwab@suse.de \
/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