Re: backtrace() from a pthread on ARM

[lxusr <gnanasekar dot r29 at gmail dot com>]

Hi,

I tried applying this patch.. Now I see that the bt prints the message
infinitely

#0  threadFunction_2 (xyz=0x0) at common.c:46
#1  0x4002c858 in start_thread (arg=<optimized out>) at pthread_create.c:299
#2  0x40117ed0 in ?? () from /arm/lib/libc.so.6
#3  0x40117ed0 in ?? () from /arm/lib/libc.so.6
#4  0x40117ed0 in ?? () from /arm/lib/libc.so.6
.......
...

I am using glibc-2.9 and linux 2.6.28. Am I missing something?


Andrew Haley wrote:
> 
> 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.
>>>
>>>
>> 
> 
> 

-- 
View this message in context: http://old.nabble.com/backtrace%28%29-from-a-pthread-on-ARM-tp23490538p33500266.html
Sent from the Sourceware - libc-ports mailing list archive at Nabble.com.