From: C Howland <cc1964t@gmail.com>
To: newlib@sourceware.org
Subject: Re: Fw: Error in posix_spawn(3) man page
Date: Wed, 29 Dec 2021 11:59:18 -0500 [thread overview]
Message-ID: <CANk6obRjbGDrjaE_09LQNG7tWAtgdPh9s1XD8ufQpZiGokTRFA@mail.gmail.com> (raw)
In-Reply-To: <DM3P110MB0522D24ED83275B9EC07839A9A449@DM3P110MB0522.NAMP110.PROD.OUTLOOK.COM>
>
>
> ------------------------------
> *From:* Newlib <newlib-bounces+craig.howland=caci.com@sourceware.org> on
> behalf of Keith Thompson <Keith.S.Thompson@gmail.com>
> *Sent:* Tuesday, December 28, 2021 10:24 PM
> *To:* newlib@sourceware.org <newlib@sourceware.org>
> *Cc:* Keith Thompson <Keith.S.Thompson@gmail.com>
> *Subject:* Error in posix_spawn(3) man page
>
>
>
> The posix_spawn(3) man page has incorrect types for the argv and
> envp parameters for the posix_spawn and posix_spawnp functions.
>
> They're shown as
> char *const argv, char *const envp
> when they should be
> char *const argv[], char *const envp[]
>
> Suggested patch (though I'm not 100% sure how the square brackets
> are handled when generating the man page):
>
> diff --git newlib/libc/posix/posix_spawn.c newlib/libc/posix/posix_spawn.c
> index 005471fde..85bfa6477 100644
> --- newlib/libc/posix/posix_spawn.c
> +++ newlib/libc/posix/posix_spawn.c
> @@ -39,11 +39,11 @@ SYNOPSIS
> int posix_spawn(pid_t *<[pid]>, const char *<[path]>,
> const posix_spawn_file_actions_t *<[file_actions]>,
> const posix_spawnattr_t *<[attrp]>,
> - char *const <[argv]>, char *const <[envp]>);
> + char *const <[argv]>[], char *const <[envp]>[]);
> int posix_spawnp(pid_t *<[pid]>, const char *<[file]>,
> const posix_spawn_file_actions_t *<[file_actions]>,
> const posix_spawnattr_t *<[attrp]>,
> - char *const <[argv]>, char *const <[envp]>);
> + char *const <[argv]>[], char *const <[envp]>[]);
>
> DESCRIPTION
> Use <<posix_spawn>> and <<posix_spawnp>> to create a new child process
>
> ------------------------------
>
>
The square brackets as done here will work as intended (_execve_r() is done
exactly like this).
Patch looks good (both for the doc viewpoint and for the stated intent of
making it match POSIX).
Craig
next prev parent reply other threads:[~2021-12-29 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 3:24 Keith Thompson
[not found] ` <DM3P110MB0522D24ED83275B9EC07839A9A449@DM3P110MB0522.NAMP110.PROD.OUTLOOK.COM>
2021-12-29 16:59 ` C Howland [this message]
2022-01-05 11:46 ` Corinna Vinschen
2022-01-05 21:39 ` Keith Thompson
2022-01-07 9:32 ` Corinna Vinschen
2022-01-07 19:03 ` Brian Inglis
2022-01-07 20:02 ` Keith Thompson
2022-01-08 0:01 ` Keith Thompson
2022-01-08 4:30 ` Keith Thompson
2022-01-10 8:58 ` Corinna Vinschen
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=CANk6obRjbGDrjaE_09LQNG7tWAtgdPh9s1XD8ufQpZiGokTRFA@mail.gmail.com \
--to=cc1964t@gmail.com \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).