public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mdione at grulic dot org.ar" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug manual/16402] New: Missing case in execve(2) manpage Date: Tue, 07 Jan 2014 10:28:00 -0000 [thread overview] Message-ID: <bug-16402-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16402 Bug ID: 16402 Summary: Missing case in execve(2) manpage Product: glibc Version: unspecified Status: NEW Severity: minor Priority: P2 Component: manual Assignee: unassigned at sourceware dot org Reporter: mdione at grulic dot org.ar CC: mtk.manpages at gmail dot com, roland at gnu dot org The manpage for execve(2) correctly lists EFAULT as a possible error, but seems to omit the case when it's returned because one of the pointers in the list or array for argv is invalid. It happened to me that calling execl() with two literal strings and no NULL terminator returned this error sometimes. Example: #include <unistd.h> execl("/bin/ls", "ls"); I know this is minor, but trying to fix the bug in my code I was misguided by the description in the manpage. It just seemed impossible! -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-01-07 10:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-07 10:28 mdione at grulic dot org.ar [this message] 2014-01-07 10:30 ` [Bug manual/16402] " siddhesh at redhat dot com 2014-01-07 18:42 ` mtk.manpages at gmail dot com 2014-01-07 18:57 ` mtk.manpages at gmail dot com 2014-01-07 19:38 ` mdione at grulic dot org.ar 2014-01-07 20:22 ` mtk.manpages at gmail dot com 2014-06-13 9:11 ` fweimer at redhat dot com
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=bug-16402-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).