From: Khem Raj <raj.khem@gmail.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc: include libgcc when libpthread is enabled
Date: Thu, 9 May 2013 09:40:56 -0700 [thread overview]
Message-ID: <124C3FE5-E47E-41D2-A277-B4D52AB18BE1@gmail.com> (raw)
In-Reply-To: <518BC905.3090508@windriver.com>
On May 9, 2013, at 9:04 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
> 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".)
>
No its not needed for debugging rather for unwinding and cancellations to work.
> If nobody has seen that recently, then ignore that.. it's been resolved.
>
> --Mark
>
>> p.
>>
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2013-05-09 16:59 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
2013-05-09 16:40 ` Khem Raj [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=124C3FE5-E47E-41D2-A277-B4D52AB18BE1@gmail.com \
--to=raj.khem@gmail.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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