From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Threadcreate() failure value?
Date: Wed, 30 Nov 2005 15:39:23 -0500 [thread overview]
Message-ID: <ee9e417a0511301239g5dbd92ecj494a98943baa9416@mail.gmail.com> (raw)
In-Reply-To: <438E048B.50808@lanl.gov>
> what if your create failed due to some other process having the process
> leak, and you'd like your process, which has done nothing wrong, to get
> out of the mess cleanly?
Then you will need to change the thread library and then
edit all the programs that use it to check the return values
on threadcreate and proccreate.
Russ
next prev parent reply other threads:[~2005-11-30 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 16:03 ISHWAR RATTAN
2005-11-30 18:31 ` Russ Cox
2005-11-30 19:02 ` ISHWAR RATTAN
2005-11-30 19:16 ` Russ Cox
2005-11-30 19:59 ` Ronald G Minnich
2005-11-30 20:39 ` Russ Cox [this message]
2005-11-30 20:43 ` Ronald G Minnich
2005-11-30 20:50 ` Russ Cox
2005-11-30 20:58 ` Martin Harriss
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=ee9e417a0511301239g5dbd92ecj494a98943baa9416@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).