This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Bug in builtins.def, the execve. don't use execle, use execel.
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'J.C. Pizarro'" <jcpiza at gmail dot com>, <gcc at gcc dot gnu dot org>
- Date: Thu, 29 Nov 2007 14:53:43 -0000
- Subject: RE: Bug in builtins.def, the execve. don't use execle, use execel.
- References: <998d0e4a0711281611g2b008c4awb5510789274ffbc8@mail.gmail.com>
On 29 November 2007 00:12, J.C. Pizarro wrote:
> The more weird thing was "..." in middle of the C's stack from
> int execle(const char *path, const char *arg, ..., char * const envp[]);
> extracted from "man execle".
http://www.opengroup.org/onlinepubs/000095399/functions/exec.html
int execle(const char *path, const char *arg0, ... /*,
(char *)0, char *const envp[]*/);
Note the comment markers. The last two 'arguments' are not real args, it is
just a comment to tell you what the last two parameters in the varargs list
should be equal to.
cheers,
DaveK
--
Can't think of a witty .sigline today....