Re: Crash in Apple code, not mine - what can I do?
Jon Gotow
What's the actual cause of the crash? A segmentation fault (SIGSEGV) or some other memory error could be caused by you corrupting memory, handing NSDocumentController a bad object somehow, or some other application error. My experience with crashes in AppKit is that it's usually something I've done prior to the crash that has scrambled memory or corrupted an object. Is the problem reproducible so you can chase down possibilities?
toggle quoted message
Show quoted text
- Jon On Dec 6, 2019, at 12:46 PM, Steve Mills via Groups.Io <sjmills@...> wrote: |
|