Is it possible that you're doing something bad (like a memory
stomp) in a global object's constructor? You could be in a messed-
up state before even reaching main().
Have you tried using MallocDebug at all?
No, I haven't. I'm pretty sure that we're OK in the memory stomping
department, because our code is well tested in CFM and during this
app-init sequence, there's basically no changes between the CFM and
MachO code.
I'll try MallocDebug, just for kicks... but I don't think it will help.
--
Mark D. Gerl, email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
