Re: App crashes when launched from finder, but not when launched from debugger or command line
Re: App crashes when launched from finder, but not when launched from debugger or command line
- Subject: Re: App crashes when launched from finder, but not when launched from debugger or command line
- From: Matt Gough <email@hidden>
- Date: Tue, 18 Nov 2008 17:45:33 +0100
On 18 Nov 2008, at 11:14, Rick Mann wrote:
I've discovered the problem. I was failing to initialize a member to
null, so when that object was requested, it wasn't getting (lazily)
constructed. When launching under the debugger, that member was
getting set to null, but when launched in the Finder, it was being
set to a non-zero value (always 0x7).
So, out of curiosity, how might I have found this missing
initialization using one of the tools? Could it have been found? It
seems like a malloc that initializes the memory to some invalid and
easily-noticed patter would've helped.
If this is something allocated via malloc then I don't see why it
wouldn't have been nil already (assuming MallocPreScribble isn't on).
I am sure that the default behavior of all malloc requests on Mac OS X
is to zero the block?
Matt
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden