> On Feb 23, 2015, at 3:43 PM, Kyle Sluder <k...@ksluder.com> wrote:
> 
> On Mon, Feb 23, 2015, at 02:00 PM, Bill Cheeseman wrote:
>> 
>> But I appear to have solved the problem, based on something I found by
>> doing a broader Google search. At some point I had added a breakpoint for
>> "All Exceptions." My latest Google search turned up a suggestion to limit
>> this to "Objective-C Exceptions" because of some problem with NSOpenPanel
>> in C++. As soon as I did that, all NSOpenPanel crashes stopped.
> 
> Does this mean you were misinterpreting being stopped in the debugger
> for actually having crashed?


The explanation I found via Google search was in a short article from Touch 
Code Magazine, here: 
http://www.touch-code-magazine.com/how-to-show-an-open-file-dialogue-in-cocoa/. 
The article describes this as a "crash." As I understand the article, a C++ 
exception is thrown in Xcode by a QuickView plug-in, and the article told me I 
could get back to my regularly scheduled development work simply by limiting 
the breakpoint to "All Objective-C Exceptions" instead of "All Exceptions."

The article's use of the word "crash" to describe this problem suggests that I 
am not alone in thinking of a thrown exception in the debugger as a "crash" 
where, as here, I couldn't make any sense of it and I couldn't get past it by 
continuing execution. My development work was completely stymied at that point. 
I had no reason to think that building and running a release version of my 
application would do anything other than crash at the same point. I will of 
course test my application in a release build in due course to make sure all is 
well at run time.

-- 

Bill Cheeseman - b...@cheeseman.name

_______________________________________________

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.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to