From: Corey Minyard <minyard@acm.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: SA_ONSTACK problems in the libraries.
Date: 16 Jan 1999 02:07:10 -0600 [thread overview]
Message-ID: <m2zp7j4p5d.fsf@wf-rch.cirr.com> (raw)
It have added SA_ONSTACK support to the kernel (support for separate
signal stacks). Some library fixes are required. I have
glibc-961212-1m and it has the following problems:
the /usr/include/signal.h has the ss_flag and ss_size parameters
reversed in the sigaltstack structure (as opposed to
/usr/include/asm/signal.h).
SA_ONSTACK needed to be added to /usr/include/sigaction.h
the sigaltstack() call just returns and error and doesn't do
the library call.
Who fixes these types of problems, since they are PowerPC specific?
--
Corey Minyard Internet: minyard@acm.org
Work: minyard@nortel.ca UUCP: minyard@wf-rch.cirr.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1999-01-16 8:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m2zp7j4p5d.fsf@wf-rch.cirr.com \
--to=minyard@acm.org \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).