___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.co
On Jun 2, 2015, at 02:36 , John Brownie wrote:
>
> * thread #1: tid = 0x51dfe8, 0x7fff9393b743
> libobjc.A.dylib`objc_exception_throw, queue = 'com.apple.main-thread', stop
> reason = breakpoint 1.1
Have you tried continuing after the exception? The next thing it should do is
log the exce
Things are working mostly fine with my app, but I discover an exception
if I close a document which has not been saved, and elect to discard the
document:
* thread #1: tid = 0x51dfe8, 0x7fff9393b743
libobjc.A.dylib`objc_exception_throw, queue = 'com.apple.main-thread',
stop reason = break
On Sep 15, 2014, at 2:52 PM, Keary Suska wrote:
> Yes, The exception will leave your app in an invalid state.
Thank you, I was not aware of that.
> The breakpoint catches before the exception would be logged to console.
> Simply keep clicking the "continue" button in the debugger until it outp
On 15 Sep 2014, at 21:42, Richard Charles wrote:
> I have a binding that throws an Objective-C exception but the console
> displays no output and the application does not crash but rather the
> application runs fine. Enabling NSBindingDebugLogLevel 1 does not help, the
> console still display
On Sep 15, 2014, at 2:42 PM, Richard Charles wrote:
> I have a binding that throws an Objective-C exception but the console
> displays no output and the application does not crash but rather the
> application runs fine. Enabling NSBindingDebugLogLevel 1 does not help, the
> console still disp
I have a binding that throws an Objective-C exception but the console displays
no output and the application does not crash but rather the application runs
fine. Enabling NSBindingDebugLogLevel 1 does not help, the console still
displays nothing. I am using Xcode 5.1.1 with the All Exceptions br
Ken Thomases wrote:
On Aug 25, 2009, at 2:02 PM, James Walker wrote:
When my app ran on Tiger, there was an NSInvalidArgumentException with
the reason:
"-observeValueForKeyPath:ofObject:change:context: only defined for
abstract class. Define -[NSCFString
observeValueForKeyPath:ofObject:cha
On Aug 25, 2009, at 2:02 PM, James Walker wrote:
When my app ran on Tiger, there was an NSInvalidArgumentException
with the reason:
"-observeValueForKeyPath:ofObject:change:context: only defined for
abstract class. Define -[NSCFString
observeValueForKeyPath:ofObject:change:context:]!"
When my app ran on Tiger, there was an NSInvalidArgumentException with
the reason:
"-observeValueForKeyPath:ofObject:change:context: only defined for
abstract class. Define -[NSCFString
observeValueForKeyPath:ofObject:change:context:]!"
That seemed to happen when I had 2 enabled bindings on
10 matches
Mail list logo