Re: SQLite 3 crash report - debugging help needed
Re: SQLite 3 crash report - debugging help needed
- Subject: Re: SQLite 3 crash report - debugging help needed
- From: "Jeremy W. Sherman" <email@hidden>
- Date: Sat, 18 Apr 2009 01:06:02 -0400
>
> I haven't been able to track this down to anything specific - it doesn't
> happen with any regularity or frequency, nor does it occur anywhere on my
> development machine that will allow me to track it down.
>
How did you come by this crash log? From the 0x48, it looks like it's
attempting to dereference an int passed into sqlite3VdbeExec where a pointer
should go, but that's a wild guess.
It's dying in sqlite3 code, so you have access to the source. Take advantage
of that. If you can attach to it in the debugger around the time of the
crash, you can observe the arguments passed into that last function call.
—Jeremy
On Fri, Apr 17, 2009 at 3:43 PM, Jon C. Munson II <email@hidden> wrote:
> Namaste!
>
> I'm not sure that this is the correct list to post this.
>
> My app is done in Cocoa though, with a sqlite 3 backend using CoreData to
> access/manage it.
>
> Here's the short version of the crash log (the whole log can be provided,
> but I didn't want to clutter this email with what may be useless
> over-info):
>
> Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes:
> KERN_PROTECTION_FAILURE at 0x0000000000000048 Crashed Thread: 0
>
> Thread 0 Crashed:
> 0 libsqlite3.0.dylib 0x95a677a5 sqlite3VdbeExec + 2821
> 1 libsqlite3.0.dylib 0x95a72ea2 sqlite3Step + 386
> 2 libsqlite3.0.dylib 0x95a7355d sqlite3_step + 29
> 3 com.apple.CoreData 0x905166c8 _execute + 56
> 4 com.apple.CoreData 0x90515f88 -[NSSQLiteConnection
> execute] + 632
> 5 com.apple.CoreData 0x90511e3b
> newFetchedRowsForFetchPlan_MT + 907
> 6 com.apple.CoreData 0x9050aa10 -[NSSQLCore
> objectsForFetchRequest:inContext:] + 304
> 7 com.apple.CoreData 0x9050a88d -[NSSQLCore
> executeRequest:withContext:] + 461
> 8 com.apple.CoreData 0x9050997a -
> [NSPersistentStoreCoordinator(_NSInternalMethods)
> executeRequest:withContext:] + 522
> 9 com.apple.CoreData 0x9050705b -[NSManagedObjectContext
>
> executeFetchRequest:error:] + 587
> 10 com.apple.AppKit 0x960df4e8 -[_NSManagedProxy
> fetchObjectsWithFetchRequest:error:] + 147
> 11 com.apple.AppKit 0x95f81923 -
> [NSArrayController(NSManagedController)
> _performFetchWithRequest:merge:error:] + 76
> 12 com.apple.AppKit 0x960dea13 -
> [NSObjectController(NSManagedController)
> fetchWithRequest:merge:error:] + 209
> 13 com.apple.AppKit 0x960dea99 -
> [NSObjectController(NSManagedController)
> _executeFetch:didCommitSuccessfully:actionSender:] + 106
> 14 com.apple.AppKit 0x9620e03e
> _NSSendCommitEditingSelector + 66
> 15 com.apple.AppKit 0x95ff4d54 -[NSController
> _controllerEditor:didCommit:contextInfo:] + 197
> 16 com.apple.CoreFoundation 0x95581a3d __invoking___ + 29
> 17 com.apple.CoreFoundation 0x95581428 -[NSInvocation invoke] +
>
> 136
>
> I haven't been able to track this down to anything specific - it doesn't
> happen with any regularity or frequency, nor does it occur anywhere on my
> development machine that will allow me to track it down. In short, it
> seems
> to just "happen."
>
> Anyone have any idea how to address this problem???
>
> Thanks in advance!
>
> Peace, Love, and Light,
>
> /s/ Jon C. Munson II
>
>
> _______________________________________________
>
> 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
>
_______________________________________________
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