From: boehm.igor@gmail.com
To: 9front@9front.org
Cc: boehm.igor@gmail.com
Subject: [9front] getpid(2) patch
Date: Wed, 23 Dec 2020 15:16:50 +0100 [thread overview]
Message-ID: <2C3AA8EF0AAF83E381CBE51F21CD53D1@gmail.com> (raw)
Fix inconsistency between man page of getpid() with its
implementation.
On 9front getpid() doesn't fail to generate a pid. Therefore it also
doesn't set errstr. Hence the text in the man page describing that
could be removed unless I am overlooking something.
If the text is left in, it suggests that one has to implement error
handling code for a situation that can never arise, at least not on
9front.
See '/sys/src/9/port/proc.c:1772: pidadd(long pid)' for details.
Thanks cinap for clearing up my initial confusion.
diff -r 568e6c7e12ac sys/man/2/getpid
--- a/sys/man/2/getpid Wed Dec 23 02:32:13 2020 +0100
+++ b/sys/man/2/getpid Wed Dec 23 15:04:09 2020 +0100
@@ -26,8 +26,3 @@
.IR intro (2),
.IR exec (2),
.IR proc (3)
-.SH DIAGNOSTICS
-Returns 0 and
-sets
-.I errstr
-if unsuccessful.
reply other threads:[~2020-12-23 14:20 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=2C3AA8EF0AAF83E381CBE51F21CD53D1@gmail.com \
--to=boehm.igor@gmail.com \
--cc=9front@9front.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).