This is the mail archive of the
mailing list for the Archer project.
Re: [python] leaks from pretty printers
- From: Paul Pluzhnikov <ppluzhnikov at google dot com>
- To: Phil Muldoon <pmuldoon at redhat dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, archer at sourceware dot org, Jeffrey Yasskin <jyasskin at google dot com>
- Date: Tue, 24 Feb 2009 10:54:40 -0800
- Subject: Re: [python] leaks from pretty printers
I've edited the subject of this thread ...
On Tue, Feb 24, 2009 at 10:35 AM, Phil Muldoon <firstname.lastname@example.org> wrote:
> Paul Pluzhnikov wrote:
>> Here is what I see after 'git pull' and rebuild today:
> Thanks, I'll look at the log in more detail. I'm kind of curious if we
> include the python suppression here:
I don't see anything there that would suppress any of the leaks in
> if we could narrow down the number of leaks. My brief smoke test (attached
> output) with suppressions shows some areas of interest. It is by no means
> comprehensive, though.
It looks like you are using --with-pymalloc python (the default),
and it looks like this many be preventing VG from accurate leak
Also, you probably would want to increase VG --num-callers parameter
from default 10, so you can see which parts of GDB are causing the
17336-byte possible leak.