Re: crash in
Re: crash in
- Subject: Re: crash in
- From: Chris Ridd <email@hidden>
- Date: Fri, 24 May 2013 19:15:45 +0100
On 24 May 2013, at 18:31, Martin Hewitson <email@hidden> wrote:
> 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
The file may be quite valid, but the parser is trying to decode an unsigned 64-bit integer into an actual variable. So maybe there's some issue with a really big (or somehow mangled) integer?
Try setting a breakpoint on strtoull_l and see what kind of arguments it is getting.
Chris
_______________________________________________
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>) |
| >Re: crash in (From: Martin Hewitson <email@hidden>) |