I didn't exactly understand which problem are you referring to, but the comments there give me a couple of ideas for slightly easier debugging, so thanks for that. For example, maybe i'll try to use less global variables.
However, unlike the program described there, this is a static analyzer - it is not designed to run continually, but to process a dump and that's all. The trouble is that with MediaWiki dumps that have several tens of thousands of pages the program runs out of memory and never finishes processing the whole dump. (FWIW this machine has 2 GB of RAM.)
So the problem is probably not the same and my question still stands - is there a way to inspect all the variables of a program and the modules that it uses and find out their memory consumption?
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.