All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: sparclinux@vger.kernel.org
Subject: sigreturn on sparc64
Date: Wed, 24 May 2006 18:00:59 +0000	[thread overview]
Message-ID: <e5270r$q83$1@terminus.zytor.com> (raw)

I'm having an issue with klibc on sparc64 (i.e. a 64-bit userspace
binary), which doesn't appear on sparc32:

If I leave the signal restorer function as NULL, I get a SIGSEGV on
attempting to return from the signal handler.

If I generate a system call stub for rt_sigreturn, and pass that in as
the restorer, then the process will loop forever on signal handler
return.

A lot of architectures have ugly corners in this area (i386, for
example, needs to drop one word from the stack before calling the
sigreturn system call.)  However, I simply don't understand the SPARC
architecture well enough to understand if/what I'm supposed to do
here, or if this is simply a bug.

	-hpa


             reply	other threads:[~2006-05-24 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 18:00 H. Peter Anvin [this message]
2006-05-24 21:21 ` sigreturn on sparc64 David Miller
2006-05-24 21:23 ` H. Peter Anvin
2006-05-24 21:34 ` David Miller
2006-05-24 22:02 ` H. Peter Anvin

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='e5270r$q83$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.