Win32 process group kill

Twice since I've resumed smoking again recently (hard drive warranty 
replacement), the batch file and Perl smoke script responsible for driving 
blead smoking have been terminated.  Since the batch file is an infinite 
loop there is no way it should have exited, unless the Perl process group 
kill tests are a little overzealous.

In theory it could be the test watchdog catching the blead Win32 test hang 
(that I have to manually kill the test usually) and doing a process group 
kill that whacks the smoker too.

There's also the Module-Build compat.t test failing under normal/no-thread 
build that is likely the offender.


I'll also be setting up either a Windows 8 64-bit or Windows XP 64-bit 
smoker soon.  I have the Windows XP 64-bit already but want to see if I 
can get a Windows 8 via the university first.


-- 
George Greer

• Win32 process group kill by George Greer