develooper Front page | perl.perl5.porters | Postings from November 2003

Re: [perl #24463] DBI tests fail with perl 5.8. 2 and -Duseithreads -Dusemultiplicity -Duse64bitint

Thread Previous | Thread Next
Nick Ing-Simmons
November 14, 2003 02:02
Re: [perl #24463] DBI tests fail with perl 5.8. 2 and -Duseithreads -Dusemultiplicity -Duse64bitint
Message ID:
Rafael Garcia-Suarez <> writes:
>Nick Ing-Simmons wrote:
>> Enache Adrian <> writes:
>> >On Thu, Nov 13, 2003 a.d., Rafael Garcia-Suarez wrote:
>> >> Well, the original problem is at
>> >>
>> >> 
>> >> 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.

That was why I created it, but now it is there...

>Anyway, it could be usable for this purpose, but when not under ithreads
>is does a newSVpvn.

Well printf-oids need to allocate space somehow - or use big fixed 
sized buffer.

>Then we could replace all "DEBUG_XXX(PerlIO_printf(Perl_debug_log,...))"
>by "DEBUG_XXX(PerlIO_debug(...))"

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About