From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] thread(2) man page
Date: Mon, 3 Sep 2007 09:23:30 -0400 [thread overview]
Message-ID: <674d5144a25f273c1f0c640ee7c75e1a@plan9.bell-labs.com> (raw)
In-Reply-To: <20070903083426.GA942@bricktop.telesystem.com>
> just to state it. We have int as return type for procexecl, procexec
> in the thread(2) man page and void in /sys/src/libthread/exec.c
If it returns at all, there was an error. If it doesn't return, there
may or may not be an error, but you won't see it.
Exec() probably has the int return value for historical reasons. I've
never seen code test for it. What you see is:
exec(...);
sysfatal("something went badly wrong: %r");
Sape
next prev parent reply other threads:[~2007-09-03 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 8:34 Markus Sonderegger
2007-09-03 13:23 ` Sape Mullender [this message]
2007-09-04 15:42 ` Douglas A. Gwyn
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=674d5144a25f273c1f0c640ee7c75e1a@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.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).