in reply to Re^2: Alternate for "open"
in thread Alternate for "open"
You've now been given several suggestions:
In particular, does your code contain use strict; and use warnings;?
It's not an completely unreasonable idea to try to measure the memory footprint of your hash, but most monks here would not do that to find the problem. Better to simplify your code so you can identify the problem.
Just remove everything until it runs properly, then start adding stuff back in. If it is a really large and ugly codebase, take the opportunity to refactor and move code out into modules. This is better practise for many reasons and will help you do this kind of debugging by making it easy to use and not use parts of the code.
You could also:
There, now you have a bunch more suggestions. It will be nice to hear back from you when you've tried some of them and you are still stuck.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Alternate for "open"
by ravi45722 (Pilgrim) on Nov 17, 2015 at 08:29 UTC | |
by Preceptor (Deacon) on Nov 17, 2015 at 11:34 UTC | |
by ravi45722 (Pilgrim) on Nov 17, 2015 at 12:51 UTC | |
by Preceptor (Deacon) on Nov 17, 2015 at 17:34 UTC | |
by Preceptor (Deacon) on Nov 18, 2015 at 14:41 UTC |