It runs just fine, even with GuardMalloc on. _However_, if I set the
MallocStackLogging env var to 1, then the app crashes, usually with
both
threads in stack_logging_log_stack().
Could it be that MallocStackLogging ruins the thread-safety of
malloc()
and free()?! Surely not...
I've certainly used MallocStackLogging with threaded apps.
I also get crashes in that location, usually when I let an app run a
long time and it runs out of space for logging. Given the number of
allocations you're making, I'll bet that's what's happening.
David Dunham Macintosh Game Developer GameHouse Studios
+1 206 926 5722 http://www.gamehouse.com
"They said it couldn't be done but sometimes it doesn't
work out that way." -- Casey Stengel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Mt-smp mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
