mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: mistake in powerpc clone.s?
Date: Thu, 26 Dec 2013 22:42:01 -0500	[thread overview]
Message-ID: <20131227034201.GE24286@brightrain.aerifal.cx> (raw)
In-Reply-To: <687A82F2-D0DB-48DF-8027-CFAC49F93B9C@mac.com>

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


  reply	other threads:[~2013-12-27  3:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26 22:08 James Gregurich
2013-12-27  1:57 ` John Spencer
2013-12-27  3:13   ` James Gregurich
2013-12-27  3:42     ` Rich Felker [this message]
2013-12-27  3:45       ` James Gregurich
2013-12-27 22:34         ` James Gregurich

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=20131227034201.GE24286@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).