Todd Fisher wrote:

> I did some more digging into this problem. It looks like the problem
> is in getDefaultMemoryPool
>

Todd,

I haven't put much time into your traces etc. but you may have run
into a peculiarity of shared code. The calling sequence for the memory
allocator is different when compiled for debugging than when compiled
without the debugging switches and so mixing modules that were compiled
differently will give you that sort of crash.


Regards,


Ann