I've had similar problems with inherited C++ and Java code. It can be very hard to track down leaks and performance problems when they aren't really true leaks!

You don't need to find the entry point. With bad OOP, that can be very tough. I'd recommend you make a utility class and in each constructor log the constructed object with the utility class, or (simpler) just print out to STDERR when you construct things so you can analyze the output later. Debugging by STDERR is gross sometimes, but it's incredibly versatile when trying to understand what your app does.

I like to have a Util::debug function (or equivalent) that I can use to disable printouts at various levels during runtime or by changing a constant.

In reply to Re: Objects Using Up the Stack by flyingmoose
in thread Objects Using Up the Stack by graq

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.