On Thu, 2002-03-14 at 01:48, Kris Kennaway wrote:
> It should be benchmarked more thoroughly before the switch is made;
> there's only one datapoint at the moment, which isn't enough to decide
> whether it's a net win.

Another thing to watch out for:  we now force -Uusemymalloc in perl
builds because mixing malloc() implementations can lead to core dumps
when a chunk of memory is handed to the wrong version of free() (or
realloc()).  (A test of this is to use Data::Dumper->Dump() (*not*
Dumpxs()!  that is in fact the workaround...) to print lots of complex
hashes; this fairly reliably makes perl dump core (or sometimes just die
with a "Bizarre copy of ...") on all our supported platforms when perl's
malloc() is used.  Of course, that might just be a bug in 5.00503, since
I never tried 5.6.x with perl's own malloc()...)

brandon s. allbery   [os/2][linux][solaris][japh]  [EMAIL PROTECTED]
system administrator      [WAY too many hats]        [EMAIL PROTECTED]
electrical and computer engineering                                KF8NH
carnegie mellon university  ["better check the oblivious first" -ke6sls]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to