Re: "exec" procedures don't handle the optional parameters unbounded situation?

[Andy Wingo]

> On Fri, Dec 16, 2011 at 3:19 AM, Ludovic Courtès <address@hidden> wrote:
>
>     Nala Ginrut <address@hidden> skribis:
>    
>     > I found "exec" serial procedures didn't check the unbounded optional
>     > parameters.
>     > (execlp "ls")  ==> segment fault
>    
>     What you’re seeing here is SIGABRT, not SIGSEGV, preceded by the message:
>    
>      A NULL argv[0] was passed through an exec system call.
>    
>     That message comes from Gnulib’s ‘set_program_name’ [0], which is used
>     by all GNU Coreutils program, and which aborts when argv[0] is NULL.

I had thought at first that this SIGABRT / SIGSEGV came from Guile
itself, in which case this would be a bug, but as it comes from `ls', I
also think that the current code is the correct code.

For what it's worth :-)

Andy
-- 
http://wingolog.org/