Re: catch signals after calling execve()

[Chet Ramey]

Roman Rakus wrote:
> After changing catching signals in bash - added CATCH_SIGNALS () macro -
> we aren't catching them after calling execve(). This short patch fix it:
> diff -up bash-3.2/execute_cmd.c.execve_catch_signal bash-3.2/execute_cmd.c
> --- bash-3.2/execute_cmd.c.execve_catch_signal  2008-09-15
> 12:20:18.000000000 +0200
> +++ bash-3.2/execute_cmd.c      2008-09-15 12:20:55.000000000 +0200
> @@ -3943,6 +3943,7 @@ shell_execve (command, args, env)
>   SETOSTYPE (0);               /* Some systems use for USG/POSIX
> semantics */
>   execve (command, args, env);
>   i = errno;                   /* error from execve() */
> +  CATCH_SIGNALS ();
>   SETOSTYPE (1);

?

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/