GC failure w/ THREAD_LOCAL_ALLOC ?

Mon Apr 1 08:53:00 GMT 2002

> -----Original Message-----
> From: Michael Smith [mailto:msmith@spinnakernet.com]
> With the rest of the changes applied, I can no longer replicate the 
> problem using GCTest.
>Great! Thanks for checking that.
>> Do you recommend running without GC_IGNORE_GCJ_INFO now that 
> this fix is in?
>Yes, I would no longer set the environment variable. For at least 9 out of
10 applications it won't matter. The relative speed is probably platform
dependent. But every once in a while you may find one that introduces
enough misidentified pointers to cause appreciable leakage. (In my
experience, this tends to be fairly testable, i.e. it's usually more a
property of the application than the input, but still ...) In the absence
of known bugs, I would always use the available type information.
Hans