You may be right to some extent in your XY supposition but nonetheless I think that a structured dump could be very helpful. This is especially the case because of the problem that I have of memory growth, where a (logical) diff between two snapshots could prove informative.

The application in question has nearly 300 Perl modules and uses several hundred from CPAN. I do not really have much idea of the source of the problem. Yes, I may be able to narrow it down using DProf but memory use and CPU-use may not be all that well correlated.

Interactive debugging is pretty much out as the application is single-threaded and has to operate in real time - delays of more than a few hundred milliseconds are fatal, although I can probably get into a sufficiently quiesced state for the few seconds that would be necessary to generate a dump

I have read perlguts (twice) and other similar material but not found what I am looking for (yet). What I need is a way to walk the heap, finding every Perl variable. If I could work out how to do that then writing a dumper should not be too hard.

---

---

• 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> <u> <ul>

• 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 intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.