Hello there,
I found this part interesting in the code: 1537 if ($is_mswin || $is_vms) { 1538 # On Windows, try to get the 'real' PID 1539 if ($is_mswin) { 1540 eval { require Win32; }; 1541 if (defined(&Win32::GetCurrentProcessId)) { 1542 $pid_to_kill = Win32::GetCurrentProcessId(); 1543 } 1544 } If it tries to load specific platform code, why not try to use the Win32 API to take care of creating and removing a process (see Win32::Process)? Regards, Alceu Em Domingo, 10 de Agosto de 2014 16:25, bulk 88 <bul...@hotmail.com> escreveu: > > > > >---------------------------------------- >> Date: Thu, 7 Aug 2014 13:57:48 +0100 >> From: da...@cantrell.org.uk >> To: cpan-testers-discuss@perl.org >> Subject: Re: How do you handle a perl process that never seems to exit? >> >> On Thu, Aug 07, 2014 at 08:29:41AM -0400, Dave Horner wrote: >> >>> it seems to happen more on windows than other platforms... >> >> Unfortunately I know exactly --><-- that much about Windows so can't >> help with that - although I'm sure you could write a watchdog thingy in >> perl if you don't have a decent shell available. > > >perl core has >http://perl5.git.perl.org/perl.git/blob/10380cb3585f27510276b532ec6e5450d1b16391:/t/test.pl#l1513 > > >