From: Daniel Jacobowitz <drow@false.org>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: Benedikt Spranger <b.spranger@linutronix.de>,
gdb@sourceware.org, Marc Kleine-Budde <mkl@pengutronix.de>,
Luotao Fu <lfu@pengutronix.de>
Subject: Re: thread-debuging with gdbserver on ARM/NPTL
Date: Wed, 25 Oct 2006 15:03:00 -0000 [thread overview]
Message-ID: <20061025150344.GA20038@nevyn.them.org> (raw)
In-Reply-To: <20061025144529.GQ18636@pengutronix.de>
On Wed, Oct 25, 2006 at 04:45:29PM +0200, Robert Schwebel wrote:
> Here are some more details about the problem. It turned out that it
> works if you link against libpthread dynamically and doesn't with
> -static.
Oh, right. Thread debugging of static applications using NPTL is
particularly problematic. Take a look at this, for starters:
http://sourceware.org/bugzilla/show_bug.cgi?id=2696
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-25 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 18:29 Benedikt Spranger
2006-10-24 18:34 ` Daniel Jacobowitz
2006-10-25 14:46 ` Robert Schwebel
2006-10-25 15:03 ` Daniel Jacobowitz [this message]
2006-10-26 9:55 ` Luotao Fu
2006-10-26 12:22 ` 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=20061025150344.GA20038@nevyn.them.org \
--to=drow@false.org \
--cc=b.spranger@linutronix.de \
--cc=gdb@sourceware.org \
--cc=lfu@pengutronix.de \
--cc=mkl@pengutronix.de \
--cc=r.schwebel@pengutronix.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