Front page | perl.perl5.porters |
Postings from November 2003
Nick Ing-Simmons wrote: > > Enache Adrian <enache@rdslink.ro> writes: > >On Thu, Nov 13, 2003 a.d., Rafael Garcia-Suarez wrote: > >> Well, the original problem is at > >> http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-10/msg01449.html > >> > >> In fact what was wanted (and implemented by this patch) is the ability to > >> access the PerlIO API early during the cloning -- to be used by debugging > >> flags (-D) for example. > > > >The whole idea of using PerlIO printing functions (which do malloc > >a lot themselves and mess with perl's internal state) to track > >leaking mallocs is at least curious :-) > > PerlIO_debug() is a printf-oid that is a little easier to use that way. I thought it was only to test PerlIO itself. Anyway, it could be usable for this purpose, but when not under ithreads is does a newSVpvn. Then we could replace all "DEBUG_XXX(PerlIO_printf(Perl_debug_log,...))" by "DEBUG_XXX(PerlIO_debug(...))"Thread Previous | Thread Next