All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Kennon Bittick <kennonlbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [bug] Error in mprotect man page description of return value
Date: Thu, 30 May 2013 12:58:56 +0200	[thread overview]
Message-ID: <51A730F0.3050508@gmail.com> (raw)
In-Reply-To: <CAMJx9yDV3ez0UzqsNn_ub9tOGGVJsN11LkDz_r_VQqC0NW3CGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 05/29/13 00:30, Kennon Bittick wrote:
> Hello,
> 
> I would like to report what I believe is an error in the man page of
> mprotect. The description of the return value says:
> 
> "Upon successful completion, mprotect() shall return 0; otherwise, it
> shall return -1 and set errno to indicate the error."
> 
> However, in my use the behavior does not match this. I reviewed the
> source code, and it appeared to match my experience rather than the
> man pages' description. Instead, the function returns (error_code *
> -1) and does not change errno.
> 
> I am new to bug reporting, so I apologize if I have made a mistake in
> the format or content of the report. Thank you.

Kennon,

How are you calling mprotect()? The wrapper function does the 
manipulation of errno. See syscalls(2).

Cheers,

Michael

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

           reply	other threads:[~2013-05-30 10:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAMJx9yDV3ez0UzqsNn_ub9tOGGVJsN11LkDz_r_VQqC0NW3CGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]

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=51A730F0.3050508@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=kennonlbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.