On Mon, 05 Apr 2010, Bill Luebkert wrote: > Jan Dubois wrote: > > > > I can't reproduce the problem with either build 1006 nor 1007 > > (the only 5.10.1 builds of ActivePerl released so far), so I have > > no idea why this is failing for you. > > > > I checked both Windows XP and Windows 7, FWIW. > > I can reproduce it in 5.8 B820.
Yes, I can do that too, but it is not very interesting as the Changelog already explains that kill(0, $pid) was broken in 820 and fixed in 822 (821 was an HP-UX specific build): http://docs.activestate.com/activeperl/5.8/changes.html#build_822_wednesday__aug_1__2007 If you dig into the bug report, you'll see that it was also broken in build 5.10.0.1000 (which was just a beta release), but should have been fixed in build 1001: http://bugs.activestate.com/show_bug.cgi?id=67519 Octavian explicitly mentioned that he was using Perl 5.10.1, which means build 1006 or 1007. [...] > I get similar weird returns from OpenProcess using API. Could you elaborate on that? Cheers, -Jan _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
