All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page execve.2
Date: Wed, 1 Nov 2023 16:27:12 +0100	[thread overview]
Message-ID: <ZUJuUJV_ztcfQeC6@debian> (raw)
In-Reply-To: <ZUJaYiMc1nM_GhB3@meinfjell.helgefjelltest.de>

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Hi Helge,

On Wed, Nov 01, 2023 at 02:02:10PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    NULL pointer → NULL

Thanks for the report!  I applied a slightly different fix:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=1bd990b3bee5fa83824f341a2cdd5a446267b09b>

Cheers,
Alex

> 
> "I<argv> is an array of pointers to strings passed to the new program as its "
> "command-line arguments.  By convention, the first of these strings (i.e., "
> "I<argv[0]>)  should contain the filename associated with the file being "
> "executed.  The I<argv> array must be terminated by a NULL pointer.  (Thus, "
> "in the new program, I<argv[argc]> will be NULL.)"
> 
> "I<envp> is an array of pointers to strings, conventionally of the form "
> "B<key=value>, which are passed as the environment of the new program.  The "
> "I<envp> array must be terminated by a NULL pointer."

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-11-01 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 14:02 Issue in man page execve.2 Helge Kreutzmann
2023-11-01 15:27 ` Alejandro Colomar [this message]

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=ZUJuUJV_ztcfQeC6@debian \
    --to=alx@kernel.org \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.