From: Steve Beaty <beaty@emess.mscd.edu>
To: froese@gmx.de (Edgar Toernig)
Cc: beaty@emess.mscd.edu (Steve Beaty), linux-kernel@vger.kernel.org
Subject: Re: sigaction, fork, malloc, and futex
Date: Thu, 6 May 2004 15:47:18 -0600 (MDT) [thread overview]
Message-ID: <200405062147.i46LlI9t017827@emess.mscd.edu> (raw)
In-Reply-To: <20040505023852.509f5fe3.froese@gmx.de> from "Edgar Toernig" at May 05, 2004 02:38:52 AM
> Uhh... just read that POSIX actually allows that. Evil!
> I guess you're entering undiscovered land...
it's funny how often i am there :-) :-)
> No fprintf and exit in a signal handler! Use write and _exit instead.
doesn't seem to matter...
> This exit is dubious too. _exit is better.
nor does this... i know better than to use *printf and exit; i was
eager to get other's views on this...
> Good luck, you may need it - ET.
i do! :-) the code seems to work on Ultrix, Solaris, and OSX.
this doesn't imply that it should :-)
--
Dr. Steve Beaty (B80) Associate Professor
Metro State College of Denver beaty@emess.mscd.edu
VOX: (303) 556-5321 Science Building 134C
FAX: (303) 556-5381 http://clem.mscd.edu/~beatys/
next prev parent reply other threads:[~2004-05-06 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 20:15 Steve Beaty
2004-05-04 22:30 ` chris
2004-05-04 22:56 ` Zan Lynx
2004-05-04 23:16 ` Andreas Schwab
2004-05-06 21:37 ` Steve Beaty
2004-05-06 22:22 ` Zan Lynx
2004-05-06 21:36 ` Steve Beaty
2004-05-04 23:37 ` Richard B. Johnson
2004-05-06 21:41 ` Steve Beaty
2004-05-05 0:38 ` Edgar Toernig
2004-05-06 21:47 ` Steve Beaty [this message]
[not found] <1SeIE-Dy-17@gated-at.bofh.it>
[not found] ` <1ShG9-2Yt-11@gated-at.bofh.it>
2004-05-04 23:57 ` Pascal Schmidt
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=200405062147.i46LlI9t017827@emess.mscd.edu \
--to=beaty@emess.mscd.edu \
--cc=froese@gmx.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®