From: Ralf Baechle <ralf@linux-mips.org>
To: libc-hacker@sources.redhat.com
Subject: Signal handler arguments
Date: Tue, 17 Sep 2002 20:20:00 -0000 [thread overview]
Message-ID: <20020918052025.A23294@linux-mips.org> (raw)
I'm revamping the sycall interfaces of the 64-bit Linux/MIPS kernel. So
far the 32-bit MIPS kernel is calling all non rt-signal handlers as:
handler(signr, 0, struct sigcontext *)
The rt-signal handlers (setup with SA_SIGINFO) get invoked as:
handler(signr, struct siginfo *, struct ucontext *)
What do applicable standards say about the arguments passed to signal
handlers? I'd like to settle with just the second signal handler type as
the x86-64 port seems to do but I'm a bit nervous that this might break
application code or standard compliance.
Can anybody shed light into this? Thanks,
Ralf
next reply other threads:[~2002-09-18 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 20:20 Ralf Baechle [this message]
2002-09-17 21:06 ` Ulrich Drepper
2002-09-17 22:15 ` Roland McGrath
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=20020918052025.A23294@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=libc-hacker@sources.redhat.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.
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).