[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <FB9D99E4-2058-4D66-A618-5A04444840F0@mac.com>
Date: Thu, 26 Dec 2013 21:45:40 -0600
From: James Gregurich <bayoubengal@....com>
To: musl@...ts.openwall.com
Subject: Re: mistake in powerpc clone.s?
If you want me to try a patch, let me know.
BTW: I have an actual crash in my app that appears to be a stack corruption. I was following up on that message to see if it was relevant to the crash.
-James
On Dec 26, 2013, at 9:42 PM, Rich Felker <dalias@...ifal.cx> wrote:
> On Thu, Dec 26, 2013 at 09:13:59PM -0600, James Gregurich wrote:
>>
>>
>> When I debug my app in gdb, I consistently get “Backtrace stopped:
>> previous frame inner to this frame (corrupt stack?)” at the lower
>> end of the backtrace. I set break points at each function in the
>> back trace and that message persists up to the __clone() invocation.
>> until that line that I pointed out, the backtrace is normal. Once
>> that instruction is executed, the backtrace is permanently broken
>> for that thread.
>
> In the backtrace for a thread other than the main thread, it's normal
> and expected for the backtrace to end at __clone; it's where the
> thread started. The "corrupt stack" message is unwanted (musl should
> be arranging for the frame pointer to be zero so that debuggers
> recognize that there's nothing else on the stack, and maybe this needs
> fixing) but I don't think it's necessarily indicative of any bug.
>
> Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
