If it is a run away loop, he should get error "fork didn't work: Resource temporarily unavailable"
I'm not going to venture a guess at this point. The error message you suggested doesn't show up in perldiag. And here is the message the original post suggested he's seeing:
I get an error "The instruction at ####### referenced memory at #######. The memory could not be read."
That message also doesn't appear in perldiag.
perlbug states: Check in perldiag to see what any Perl error message(s) mean. If message isn't in perldiag, it probably isn't generated by Perl. Consult your operating system documentation instead.
Since the OP's error message isn't listed in perldiag, I can only assume that it's either generated by a module, or by the operating system. We haven't been told what modules are in use. The original post also doesn't mention what operating system the code is running on. So we know we're not seeing a Perl error (assuming the OP gave us the correct error message), but that's about all we know for sure. The code snippet provided leaves open the possibility of a runaway loop. But it also leaves a lot of other possibilities that need clarification.
No more guesses from me until we get more details. It's probably way premature to assume a Perl bug though. ;)
Dave
In reply to Re: Re: Re: forking memory problem
by davido
in thread forking memory problem
by sacco
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |