This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: backtrace() from a pthread on ARM
- From: Andrew Haley <aph at redhat dot com>
- To: libc-ports at sourceware dot org
- Date: Tue, 13 Mar 2012 15:32:57 +0000
- Subject: Re: backtrace() from a pthread on ARM
- References: <be62573b0905111306j50989697k755312d6e4fdd5e3@mail.gmail.com> <20090511201238.GA12032@caradoc.them.org> <be62573b0905111336y4a664f42v21aa2b21f9252623@mail.gmail.com> <m2eiuu1xf9.fsf@igel.home> <be62573b0905120854w4c1269f4r6698e231b9b4ff6e@mail.gmail.com> <m2zldil2w2.fsf@igel.home> <be62573b0905120924x5a943ebfue3eba03c77fa404d@mail.gmail.com> <33492571.post@talk.nabble.com> <4F5F108E.7010204@redhat.com> <33494793.post@talk.nabble.com>
On 03/13/2012 03:20 PM, lxusr wrote:
>
> If i keep a breakpoint in a threadfunction and do a bt, I see this,
>
> #1 0x4002c858 in start_thread (arg=<optimized out>) at pthread_create.c:299
> #2 0x40117eb0 in clone () from /arm/lib/libc.so.6
> #3 0x40117eb0 in clone () from /arm/lib/libc.so.6
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
I fixed that one a long time ago. See
http://sourceware.org/ml/libc-ports/2011-08/msg00000.html
> Andrew Haley wrote:
>>
>> On 03/13/2012 07:50 AM, lxusr wrote:
>>> I am facing a similar problem wherein if I do a bt I see corrupted stack
>>> whenever clone gets called(ARM target). Can you please tell me what is
>>> the
>>> fix you applied to resolve the problem?
>>
>> Corrupted how, exactly? What is the symptom?
>>
>> Andrew.
>>
>>
>