d'oh, wrong reply button. :-(
Begin forwarded message:
From: muppet <[EMAIL PROTECTED]> Date: Thu May 27, 2004 8:09:38 AM US/Eastern To: [EMAIL PROTECTED] Subject: Re: Bumping ref count on a parent object
On Thursday, May 27, 2004, at 02:38 AM, Tassilo von Parseval wrote:
On Wed, May 26, 2004 at 10:55:09PM -0700 Bill Moseley wrote:
So, this shows leaks -- are those my errors or are they in Perl? I'm guessing Perl because:
valgrind --leak-check=yes perl -le "$x = 1"
shows lost memory. But, I'm not so sure -- if I comment out my "safefree()" call in my .xs code the report changes only slightly.
Perl doesn't free all memory when shutting down. Usually there's no need
for it since on exit the OS will do the clean up.
you can make valgrind useful again by finding which of these leaks are always there and adding them to a suppression file. i have a rather large one that includes perl, Xlib, and Gtk+, if you'd like it.
As for non-reported obvious memory leaks, I also have some difficulties in getting a reported memory leak with SVs. I don't know why they are not reported.
could it have to do with SVs being allocated in perl's private heap?
-- I don't have a drinking problem, 'cept when i can't get drink. -- Tom Waits
-- elysse (in labor): is the head the biggest part? midwife: yes. elysse: oh, good.
