From: Mark Hatle <mark.hatle@windriver.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc: include libgcc when libpthread is enabled
Date: Thu, 9 May 2013 11:04:21 -0500 [thread overview]
Message-ID: <518BC905.3090508@windriver.com> (raw)
In-Reply-To: <1368114004.14512.417.camel@phil-desktop.brightsign>
On 5/9/13 10:40 AM, Phil Blundell wrote:
> On Thu, 2013-05-09 at 10:26 -0500, Mark Hatle wrote:
>> This would be my suggestion. I'd also want to make sure there is a
>> libpthread-dev (which for some reason I think there already is) because the
>> links in there are required for on-target thread debugging...
>
> Really? If those links are needed for thread debugging then it sounds
> like they should be in libthread-db, not in any -dev package.
I'm pretty sure I'm misremembering the issue. It's the libthread-db that needs
the link for debugging. Last time I was playing with this was pre-Denzil and it
didn't quite work right. (gdb on the target debugging threads would say "hey I
need the ....so to debug".)
If nobody has seen that recently, then ignore that.. it's been resolved.
--Mark
> p.
>
>
next prev parent reply other threads:[~2013-05-09 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 12:55 [PATCH] eglibc: include libgcc when libpthread is enabled Bogdan Marinescu
2013-05-09 13:19 ` Richard Purdie
2013-05-09 14:32 ` Phil Blundell
2013-05-09 13:20 ` Phil Blundell
2013-05-09 13:28 ` Marinescu, Bogdan A
2013-05-09 14:08 ` Phil Blundell
2013-05-09 15:02 ` Phil Blundell
2013-05-09 14:25 ` Khem Raj
2013-05-09 14:32 ` Khem Raj
2013-05-09 15:26 ` Mark Hatle
2013-05-09 15:36 ` Richard Purdie
2013-05-09 15:40 ` Phil Blundell
2013-05-09 16:04 ` Mark Hatle [this message]
2013-05-09 16:40 ` Khem Raj
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=518BC905.3090508@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.