Front page | perl.perl5.porters |
Postings from April 2007
On Tue, 17 Apr 2007, Steve Hay wrote: > Garrett Cooper wrote: >>>> Jan Dubois wrote: >>>>> I broke the kill(0, $pid) behavior on Windows with change 29605 >>>>> (the one implementing killpg()): >>>>> >> >> Speaking of kill... have you guys tried running kill(0, undef) with certain >> versions of Perl? The earlier versions (5.8.2) apparently killed the parent >> process instead of erroring out or something. >> >> You just reminded me of that point. > > I can't reproduce anything like what you describe with 5.6.0, 5.6.1, any 5.8.x > or bleadperl. I tried running > > perl -le "print kill(0, undef); print 'Hi'" > > with each of those perls, and they all print 'Hi' okay. Is this one-liner > sufficient to show up the problem concerned? > > I'm running on Windows XP. What OS have you seen this problem on? It exists with XP SP2, and although Cygwin's POSIX compliant to some extent, is Windows? Try this: perl -e 'kill 15, undef; print "Hello, cruel world!";' And yes, I was the person that originally sent the bug report. If someone could provide me with the POSIX spec that says that an undefined value equals 0, and a 0 value with kill works out to kill the calling process, I'd appreciate it. Thanks, -GarrettThread Previous | Thread Next