This project has moved. For the latest updates, please go here.

code path vfork_main under WIN32

Coordinator
Jul 6, 2008 at 3:42 PM
The TEST1.BAT tries to exersize the vfork_main code path for WIN32. It does not do much.
What is is support to do is call CreateProcess 3 times, passing in the name of the command crashme.exe,
which by default is in a fairly verbose mode, which should print out a lot.
However, it does hardly anything. Note that crashme will is not fully potent when running in visual studio debug mode.
But the debug mode is useful when tracking down these basic flow of control problems.

C:\temp>crashme 8192 666 0 -3
Crashme: (c) Copyright 1990-1994 George J. Carrette
Version: 2.4 20-MAY-1994
crashme 8192 666 0 -3
Creating -3 crashme subprocesses
Test complete, total real time: 0 seconds (0 00:00:00)
exit status ... number of cases
Coordinator
Jul 6, 2008 at 9:41 PM

Most recent source code check fixes things up. CreateProcess call did not return proper error message. Crashme.exe is best invoked with a pathname that is fully qualified but without spaces in folder names. TEST1.BAT sets this up ok. Output should look something like this (taken from crashme.log)

Test complete, total real time: 38 seconds (0 00:00:38)
exit status ... number of cases
-1073741783 ...     1
-1073741794 ...     1
-1073741795 ...     7
 -536870911 ...     2
-1073741674 ...    15
-1073740791 ...    27
-2147483644 ...     2
-1073741819 ...    98