http://qs1969.pair.com?node_id=576934


in reply to Re^3: Win32 - Memory can not be "read"
in thread Win32 - Memory can not be "read"

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!

Replies are listed 'Best First'.
Re^5: Win32 - Memory can not be "read"
by jbert (Priest) on Oct 08, 2006 at 09: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 09, 2006 at 03: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]
      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]

In Section Seekers of Perl Wisdom