Re: Extended Save Dialog Crashing
Re: Extended Save Dialog Crashing
- Subject: Re: Extended Save Dialog Crashing
- From: Luther Baker <email@hidden>
- Date: Tue, 28 Oct 2014 07:49:49 -0500
The stack trace looks like
Thread 4
Queue: quicklook.pluginload (serial)
0 __cxa_throw
19 start_wqthread
Enqueued from com.apple.root.default-overcommit-priority (Thread 12)
0 _dispatch_barrier_async_f_slow
10 thread_start
but nothing is logged to the console ... which makes me wonder. I hit
'continue' a few times and it keeps "breaking" and replacing my editor with
the assembly I pasted before. I notice I've got a breakpoint to catch "All
Exceptions" ... so I turn that off and rerun and what do you know? No
problems. In fact, I put the same breakpoint in my brand new test project
and same outcome - the dialogs are throwing an internal exception.
So I guess the exception is a part of that dialog's natural code path. I've
seen Core Data use this intentional technique in certain situations as well
so seems like nothing is wrong. I just can't leave the "All Exceptions"
breakpoint on when saving or opening (or I need to provide an exception in
the breakpoint).
Thanks for driving me to find this by asking for the stack and logged
error. Will note for next time before bothering the list. App is coming
along nicely thanks to you all!
-Luther
On Tue, Oct 28, 2014 at 1:29 AM, Kyle Sluder <email@hidden> wrote:
>
>
> Sent from my iPad
>
> > On Oct 27, 2014, at 8:33 PM, Luther Baker <email@hidden> wrote:
> >
> > I'm writing my first Document based app for OSX and have reached a spot
> > where I'd like to actually save and open a file. It is a Core Data backed
> > Document within which I create some arbitrary data and display it via two
> > NSOutlineViews. I also have the ability to edit the data inline and save
> it
> > back to the screen ... so I thought I'd actually try saving and opening
> > from disk.
> >
> > Unfortunately, on my first attempt to save, I clicked the little triangle
> > to open the EXTENDED save dialog and almost immediately, the app crashed.
> > Subsequent attempts to formally save automatically open the EXTENDED save
> > dialog and immediately crash. Attempts to OPEN a file also open an
> EXTENDED
> > version of the Open dialog and crash.
> >
> > (stack trace below ...)
>
> You didn’t provide a stack trace; you pasted the disassembly for the C++
> throw statement.
>
> Can you please log the actual stack trace along with the exception that is
> logged to the console?
>
> --Kyle Sluder
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden