On Tue, Aug 3, 2010 at 3:48 PM, Greg Giacovelli <miyamo...@gmail.com> wrote: > So I have been getting actual segfaults reported on start up of my > app. However the segfault is within sqlite while opening a db which > hasn't been touched in a while. Is there something I am missing? Here > is a sample one that was sent to me recently.
Segfaults are invariably a firmware/OS failure. There's nothing a developer can do from SDK code that should result in a segfault, at least that I am aware of. If fadden does not respond to this post (and he has a remarkable gift for finding these core dump posts), post it and any other info you can supply to an issue on b.android.com. In particular: -- if you have a project that reproduces the problem, that'd be huge -- if you are getting these reports from the field, include all distinct "Build fingerprint" values, so we can better determine if the problem is unique to a handset, manufacturer, OS release, or is pervasive -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Development Wiki: http://wiki.andmob.org -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
