perl bug in win32?

Pete_I has asked for the wisdom of the Perl Monks concerning the following question:

recently while playing with perl, i stumbled upon what appears to be a bug that crashed perl. I narrowed it down to this code.

sub d{fork}
eval"&d"
[download]

I think it has todo with the fork inside eval. my perl version is Activestate v5.8.6 built for MSWin32-x86-multi-thread
has this been patched or has anyone else had a similar problem? Is this another undocumented 'feature'?

-- Pete_I

Comment on perl bug in win32? Download Code

Replies are listed 'Best First'.
Re: perl bug in win32? by vkon (Curate) on Apr 23, 2006 at 10:52 UTC
When I build perl for my own purposes, I turn off all threading, because otherwise you pay for threading (general slowdown and memory penalty, and huge memory penalty on actual thread usage) Its a waste to have threading support, but never actually using it, due to its instability. On the bright side -- perl threading now is improving, plus there are new Coverity discussions on p5p ML, that shakes down and cleans many wrong places, so our chances are improving... :) The good thing you can do -- suggest a patch to the perl's test suite, so it will be noticed by perl porters.	[reply]
Re: perl bug in win32? by spiritway (Vicar) on Apr 23, 2006 at 10:29 UTC
It crashes on ActiveState v5.8.7, build 813.	[reply]
Re^2: perl bug in win32? by Marza (Vicar) on Apr 23, 2006 at 14:21 UTC
And build 815 --edit-- And 5.8.8 build 8.17	[reply]