Re^4: Win32 - Memory can not be "read"

This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.

Thank you! +++++++ I'll see if I can somehow boil this down to a test case...if not, at least it's nice to understand what's happening a little better!

Comment on Re^4: Win32 - Memory can not be "read"

Replies are listed 'Best First'.
Re^5: Win32 - Memory can not be "read" by jbert (Priest) on Oct 08, 2006 at 05:35 UTC
If the problem is the for() bug referred to (and it seems like a good candidate) and a later version of perl doesn't have it fixed, then you could work around the problem by hacking on the module - you could try changing the for() loop to a while loop with an explicit counter on number of iterations.	[reply]
Re^5: Win32 - Memory can not be "read" by Steve_p (Priest) on Oct 08, 2006 at 23:33 UTC
I you have some example code, please please please reply to the ticket so I can reopen it. Its exeptionally hard to tell whether a bug is fixed or not without some code to test with.	[reply]
Re^6: Win32 - Memory can not be "read" by HuckinFappy (Pilgrim) on Oct 09, 2006 at 11:52 UTC
The problem is I can't consistently recreate this. It's about a .0015% occurance rate. I see around 20 failures for every 25,000 perl invocations in a build of our code base. Still trying to isolate it...	[reply]

• hippo

‥ epoptai's answer Re: how do I set a cookie and redirect was blessed by hippo!

• erzuuli

‥ Anonymous Monks are no longer allowed to use Super Search, due to an excessive use of this resource by robots.


Just another Perl shrine
	PerlMonks