public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marcus.shawcroft at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17555] New: [AARCH64][GLIBC]glibc's _start dosen't terminate the frame record chain correctly
Date: Wed, 05 Nov 2014 10:28:00 -0000	[thread overview]
Message-ID: <bug-17555-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=17555

            Bug ID: 17555
           Summary: [AARCH64][GLIBC]glibc's _start dosen't terminate the
                    frame record chain correctly
           Product: glibc
           Version: 2.20
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: marcus.shawcroft at gmail dot com
                CC: drepper.fsp at gmail dot com

In glibc-2.20/sysdeps/aarch64/start.S we find:
_start:
/* Create an initial frame with 0 LR and FP */
mov    x29, #0
mov    x30, #0
mov    x29, sp

Because of the way _start is implemented, the end of the frame record
chain is not indicated by zero but instead by the value of
argc, because that's the first value on the initial stack.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-11-05 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 10:28 marcus.shawcroft at gmail dot com [this message]
2014-11-05 10:29 ` [Bug libc/17555] " marcus.shawcroft at gmail dot com
2014-11-05 10:32 ` marcus.shawcroft at gmail dot com
2014-11-05 10:33 ` marcus.shawcroft at gmail dot com
2014-11-11 16:01 ` marcus.shawcroft at gmail dot com

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=bug-17555-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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. 
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 read-only IMAP folder(s) and NNTP newsgroup(s).