comment on

Setting PERL_VALGRIND=1 and PERL_DEBUG=1 didn't change my results.

My debugperl is built from the 5.8.8 source; grepping both that and bleadperl's source for VALGRIND didn't turn up any change in behavior; it looks like the only thing PERL_VALGRIND does is turn on some tests. A similar grep for PERL_DEBUG was produced more voluminous output which was harder to scour; nothing that would change memory management jumped out at me, though maybe I missed something.

In contrast, PERL_DESTRUCT_LEVEL affects perl_destruct in perl.c rather dramatically. Perhaps the system that this perl is built on (RedHat 9) has something to do with our divergent results.

BTW, I'm eager to improve my skills in this area, so if anyone knows some useful links, please let me know.

If you're still following p5p, you may have seen this, but there was a thread recently on running Perl's test suite under Valgrind

--
Marvin Humphrey
Rectangular Research ― http://www.rectangular.com

In reply to Re^2: Valgrind, Perl, and banishing leaks by creamygoodness
in thread Valgrind, Perl, and banishing leaks by creamygoodness

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks