Extended Save Dialog Crashing
Extended Save Dialog Crashing
- Subject: Extended Save Dialog Crashing
- From: Luther Baker <email@hidden>
- Date: Mon, 27 Oct 2014 22:33:12 -0500
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 ...)
.... but, if I click in the upper part of the toolbar and give the
window/document a name, it actually saves (albeit as a *.binary file).
Also, if I try to EXIT from the program, I am prompted to save at which
time the mini save dialog shows up and I can save as binary, sqlite or xml.
When I restart the app, I can successfully open the files I've saved via
File / Recents menu and see the changes I made via my editing. I just can't
open the EXTENDED save and EXTENDED open dialogs. If I create a new project
from scratch, the extended dialogs work just fine ... but clearly, they
don't have all the work I've done to create the views and Core Data model.
Does this problem this ring a bell with anyone? Since I can save and open
files I would think that the Extended dialogs don't like something about my
project --- but I'm not sure what that could actually be nor how to track
it down. The stack below is just most assembler into the core os.
At a minimum, is there anything I can do to actually reset the app back so
that it does not use the EXTENDED dialogs? With iOS, I would just reset the
simulator ... but I'm not sure on the desktop. Is there a plist directory
somewhere I can clean out that effectually does the same thing?
Thanks much,
-Luther
libc++abi.dylib`__cxa_throw:
0x7fff8d64abdf: pushq %rbp
0x7fff8d64abe0: movq %rsp, %rbp
0x7fff8d64abe3: pushq %r15
0x7fff8d64abe5: pushq %r14
0x7fff8d64abe7: pushq %r13
0x7fff8d64abe9: pushq %r12
0x7fff8d64abeb: pushq %rbx
0x7fff8d64abec: pushq %rax
0x7fff8d64abed: movq %rdx, %r14
0x7fff8d64abf0: movq %rsi, %r15
0x7fff8d64abf3: movq %rdi, %rbx
0x7fff8d64abf6: callq 0x7fff8d64a7f4 ; __cxa_get_globals
0x7fff8d64abfb: movq %rax, %r12
0x7fff8d64abfe: callq 0x7fff8d64b180 ; std::get_unexpected()
0x7fff8d64ac03: movq %rax, -0x60(%rbx)
0x7fff8d64ac07: callq 0x7fff8d64b1ba ; std::get_terminate()
0x7fff8d64ac0c: leaq -0x20(%rbx), %r13
0x7fff8d64ac10: leaq 0x44(%rip), %rcx ;
__cxxabiv1::exception_cleanup_func(_Unwind_Reason_Code, _Unwind_Exception*)
0x7fff8d64ac17: movabsq $0x434c4e47432b2b00, %rdx
0x7fff8d64ac21: movq %rax, -0x58(%rbx)
0x7fff8d64ac25: movq %r15, -0x70(%rbx)
0x7fff8d64ac29: movq %r14, -0x68(%rbx)
0x7fff8d64ac2d: movq %rdx, -0x20(%rbx)
0x7fff8d64ac31: movq $0x1, -0x78(%rbx)
0x7fff8d64ac39: incl 0x8(%r12)
0x7fff8d64ac3e: movq %rcx, -0x18(%rbx)
0x7fff8d64ac42: movq %r13, %rdi
0x7fff8d64ac45: callq 0x7fff8d64d9cc ; symbol stub for:
_Unwind_RaiseException
0x7fff8d64ac4a: movq %r13, %rdi
0x7fff8d64ac4d: callq 0x7fff8d64ac7f ; __cxa_begin_catch
0x7fff8d64ac52: movq -0x58(%rbx), %rdi
0x7fff8d64ac56: callq 0x7fff8d64b1c9 ; std::__terminate(void
(*)())
_______________________________________________
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