Re^3: MemLeak in Perl from C Calls

Even after almost a decade, the problem exists as it was!

Comment on Re^3: MemLeak in Perl from C Calls

Replies are listed 'Best First'.
Re^4: MemLeak in Perl from C Calls by pierremallard (Initiate) on Feb 12, 2010 at 16:08 UTC
Hi, I'm facing the same problem... It's ok since I can manage one call to perl_parse where memory leaks seems to be, with multiple call to perl_call_argv, but I'd like to have a clean memcheck output without using valgrind suppress option. Still no answers (i.e. complete perl memory free on perl_destruct before program exit) ? (I'm on Perl 5.8.8) Thanks...	[reply]