comment on

I have an application that uses literally hundreds of modules (plus in turn their dependencies). And it's a forking application, specifically a webserver.

My problem is that sometimes a child will hang with 100% CPU usage during the DESTROY call. What would be the best way to debug this?

Print statements? Setting hundreds of debug points?

Is there any good way to overload DESTROY without loosing the original functions? EDIT: To clarify, automatically adding a print "starting DESTROY in $filename"/"Ending destroy in $filename" to every DESTROY function would help quite a lot.

perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'

In reply to Debugging DESTROY calls in forking application by cavac

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.


Perl-Sensitive Sunglasses
	PerlMonks