Re: crash in
Re: crash in
- Subject: Re: crash in
- From: Martin Hewitson <email@hidden>
- Date: Fri, 24 May 2013 19:31:59 +0200
Great. I found an on-line validator (http://www.w3schools.com/dom/dom_validate.asp) and it finds no errors.
Back to the crash log: do the reported errors mean that there's something wrong with the XML file? I mean, this file is created by Core Data, by calling -saveToURL:... in the NSPersistentDocument subclass. So it's not really anything my app is doing. So unless the user somehow messed up the file, I suppose the file is in good order.
So what else could be wrong?
I was wondering about file encoding. The crash log ends with
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff8142c126 strtoull_l + 75
1 com.apple.CoreData 0x00007fff898b7878 +[_PFRoutines convertCString:toUnsignedInt64:withBase:] + 40
2 com.apple.CoreData 0x00007fff898cf3b0 -[NSXMLDocumentMap _processInstanceNode:] + 240
What if the file contains characters that can't be read given the file encoding being used by Core Data? Inspecting the file by hand, I couldn't see anything suspicious, but I couldn't swear to it.
Many thanks,
Martin
On 24, May, 2013, at 06:36 PM, Jens Alfke <email@hidden> wrote:
>
> On May 24, 2013, at 9:11 AM, Martin Hewitson <email@hidden> wrote:
>
>> The crash seems to be something to do with the XML file, but the file is >6000 lines long, so it's hard to validate it by hand
>
> There are automatic validators, including an online one run by the W3C. I can’t remember the URL but it should be pretty easy to find.
>
> —Jens
_______________________________________________
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
| References: | |
| | >crash in (From: Martin Hewitson <email@hidden>) |
| | >Re: crash in (From: Jens Alfke <email@hidden>) |