zation). It should be done
> at
> least after calling XtAppInitialize(3).
>
> It will be the main limitation for a tool like `abstain`. pledge(2) should be
> called *after* initialization, and not at the beginning of the program.
I also think that.
If we pledge(2) after initializing the connection to the X Server, we
can drop the "unix" and "inet" promises.
Lucas de Sena
On 2023-06-26, Marc Espie wrote:
> Note that a NULL environment is undefined behavior according to POSIX.
> If you read the OpenGroup description, it very clearly states that
> envp is a pointer to a NULL terminated array.
>
> Does GNU/Linux at least document that passing a NULL pointer means no
>
The manual already describes how posix_spawn(3) behaves when passing it
a NULL envp, but does not make it clear that it is an OpenBSD extension:
> If envp is NULL, the environment is passed unchanged from the parent
> process.
That differs from GNU/Linux, for example, where a NULL envp gives the
