observing invalid key aborts with LLVM
observing invalid key aborts with LLVM
- Subject: observing invalid key aborts with LLVM
- From: Roland King <email@hidden>
- Date: Thu, 16 Dec 2010 22:16:34 +0800
| I misspelled a key path in my code at the point I was registering observation. When run the code just SIGABRT'ed with no useful error message. This is iOS code and I end up with the following stack trace.
#0 0x9571d176 in __kill #1 0x9571d168 in kill$UNIX2003 #2 0x957af89d in raise #3 0x957c59bc in abort #4 0x95741f0b in _Unwind_Resume #5 0x00e69343 in CFRunLoopRunSpecific #6 0x00e69161 in CFRunLoopRunInMode #7 0x0185f268 in GSEventRunModal #8 0x0185f32d in GSEventRun #9 0x002e542e in UIApplicationMain #10 0x00001bbe in main at main.m:14
If I build with anything else, GCC LLVM, GCC etc I get a proper
*** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<CalcParser 0x4e3c920> valueForUndefinedKey:]: this class is not key value coding-compliant for the key vallid
(and yes it's funny I spelled 'valid' incorrectly) which is a little more useful. I think I've seen this before because my first thought was 'oops wrong key in KVO' and found it quite rapidly.
Is there a flag I'm missing when building with LLVM which causes this behaviour?
|
_______________________________________________
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