From: David Huggins-Daines <dhd@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] signal handling
Date: 26 Jul 2000 10:07:56 -0400 [thread overview]
Message-ID: <87puo1ougz.fsf@linuxcare.com> (raw)
Hi,
I was quite shocked to discover that we appear to have no signal
handling code in the Linux/parisc kernel whatsoever.
Is anyone planning to do this anytime soon? It's unbelievably
annoying to debug userspace when you have to push TOC every single
time your program segfaults.
Never mind the fact that we can't really claim to have a working
kernel if it lacks basic things like signals.
I am formally threatening to do it wrong (since I don't know what I am
doing) if nobody steps forward to do it correctly within the next
hour.
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
reply other threads:[~2000-07-26 14:06 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=87puo1ougz.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=parisc-linux@thepuffingroup.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 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.