This is the mail archive of the
cygwin-patches@cygwin.com
mailing list for the Cygwin project.
Re: [Patch] Fixing the PROCESS_DUP_HANDLE security hole.
On Mon, Nov 22, 2004 at 01:36:45PM -0500, Igor Pechtchanski wrote:
>On Mon, 22 Nov 2004, Christopher Faylor wrote:
>>*I've also added an 'exitcode' field to _pinfo so that a Cygwin process
>>*will set the error (sic) code in a UNIX fashion based on whether it is
>>*exiting *due to a signal or with a normal exit().
>>
>>Since a windows program can't exit "due to a signal" the only
>>alternative would be to consider it an exit code.
>
>And what I was trying to say (perhaps not as eloquently as I would have
>wished) was that it's better, IMO, to mangle the negative exit code
>from a Windows app than to let it tread on the reserved bits.
You probably want to mediate on what would possibly be meant by the term
"unix fashion". Hint: It does not mean "set some reserved bits and do
strange things with negative exit values". Maybe looking at wait.h
would be helpful.
cgf