http://qs321.pair.com?node_id=704378


in reply to Centos 5 specific DBI memory leak

Since CentOS is Linux, have you tried valgrind?

It should be able to tell you where the leaked memory was allocated, i.e. if it was from within perl or an external lib.

Replies are listed 'Best First'.
Re^2: Centos 5 specific DBI memory leak
by Krambambuli (Curate) on Aug 15, 2008 at 07:57 UTC
    I never used valgrind before, so I'm into new territories with this, but I'll probably give it a try.

    Thanks for your suggestion.

    Update: valgrind rocks! Now I just cannot understand how come I never used it till now ... ?!

    To all the fellow cowards like me (as I guess it was plain fear of yet-such-another-hard-to-use-debugging-tool that made me overlook it for so long): it's nothing to be afraid of! It's strong, but very gentle with newbies too - somewhat like Perl in this regard.

    And yes, it gave me in just a few minutes the information I was trying to find for a few days already: it's an Oracle shared library that causes my headache: libclntsh.so.9.0. Now if that isn't of help, I don't know what would be...

    Thanks again for pointing me this marveluous tool. I definitely became a fan of it in no time.