Actually I've found an other bug at the same location. If the end of the specified path was a directory with the x flag, a process was incorrectly started.
 
The new patch fixes this issue. (replaces the previous mail's patch, I hope it is not too late :p )
 
Jerome.
----- Original Message -----
Sent: Friday, February 28, 2003 12:36 AM
Subject: [Mono-list] Process.Start patch

Hi there,
 
    Here is a fix for the overloads of System.Diagnostics.Process.Start, the method CreateProcess in processes.c was not checking for the executable validity when called with a absolute path. There were also two uninitialized variables that now are set to NULL. (would have lead to multiple frees in this context)
 
Could someone commit it if ok ?
 
An other thing, a null reference should not be sent when the executable is not found. How should this be addressed ?
 
Jerome.

Attachment: processes.c.diff
Description: Binary data

Reply via email to