From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4413 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: mistake in powerpc clone.s? Date: Thu, 26 Dec 2013 22:42:01 -0500 Message-ID: <20131227034201.GE24286@brightrain.aerifal.cx> References: <6CBC4CE2-CFF2-4FE6-8DD5-6FB2B1FCBA4A@mac.com> <52BCDE8A.3060304@barfooze.de> <687A82F2-D0DB-48DF-8027-CFAC49F93B9C@mac.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1388115730 2007 80.91.229.3 (27 Dec 2013 03:42:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Dec 2013 03:42:10 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4417-gllmg-musl=m.gmane.org@lists.openwall.com Fri Dec 27 04:42:17 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VwOJT-0004Fu-O1 for gllmg-musl@plane.gmane.org; Fri, 27 Dec 2013 04:42:15 +0100 Original-Received: (qmail 10172 invoked by uid 550); 27 Dec 2013 03:42:15 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 10164 invoked from network); 27 Dec 2013 03:42:14 -0000 Content-Disposition: inline In-Reply-To: <687A82F2-D0DB-48DF-8027-CFAC49F93B9C@mac.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:4413 Archived-At: 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