Re: Hard to Debug windows memory error

Do you know whether your script is actually finishing? Or even fully getting started? Try cutting out bits of the script to see whether that has any effect and to see if you can come up with a minimal complete example that still fails that you can show us.

Comment on Re: Hard to Debug windows memory error

Replies are listed 'Best First'.
Re^2: Hard to Debug windows memory error by jandrew (Chaplain) on Dec 31, 2015 at 19:48 UTC
The very last line of my script is a print statement that does print under several tested environments. I suspect the problem is in the perl garbage collection. The difficulty is the module I'm writing using the script is is complex and multi-layered. I was hoping to get some debugging advice/techniques that I could use so that I could narrow it down to a simple script that reliably fails.	[reply]
Re^3: Hard to Debug windows memory error by kennethk (Abbot) on Dec 31, 2015 at 20:24 UTC
Try putting some print statements in END blocks: BEGIN, UNITCHECK, CHECK, INIT and END in perlmod That might help you debug the unwind. You can also create some objects with controlled scope and put diagnostics in their Destructors. #11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.	[reply]
Re^4: Hard to Debug windows memory error by jandrew (Chaplain) on Dec 31, 2015 at 23:05 UTC
kennethk thank you for your suggestion. I did already try BEGIN blocks but I had forgotten to try END blocks. When retesting a simple print statement in an END block didn't even execute. I interpret that to mean that windows killed the general perl interpreter prior to reaching the END block. I hope I read that right.	[reply]
Re^5: Hard to Debug windows memory error by kennethk (Abbot) on Dec 31, 2015 at 23:19 UTC
Re^6: Hard to Debug windows memory error by jandrew (Chaplain) on Jan 01, 2016 at 00:15 UTC
Some notes below your chosen depth have not been shown here


P is for Practical
	PerlMonks