John Indra <[EMAIL PROTECTED]> writes:
> Glad to know that there is no problem with malloc() in -CURRENT. But I still
> think that this must be addressed in Perl. So maybe, the stock Perl should
> be built against its own malloc library?
No! That would break anything that loads system libraries into Perl,
like Authen::PAM, because you'd end up calling system malloc()
followed by Perl free(), or the other way around.
Please stop pretending this is a FreeBSD bug - it's a bug in Perl,
which anally tries to conserve microscopic amounts of memory by
growing strings in small increments instead of using the traditional
(and far more efficient and elegant) 2n + 1 algorithm.
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message