Actually, SQLite is a little bit less than totally robust. There are some forms of damage to the DB file that can result in seg faults or their equivalent, eg. But I've never seen them with a healthy DB file and reasonably benign user commands (and you can't really get at the funky SQLite stuff from Android's Java).
On Aug 3, 2:53 pm, Mark Murphy <[email protected]> wrote: > On Tue, Aug 3, 2010 at 3:48 PM, Greg Giacovelli <[email protected]> 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/commonsguyhttp://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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
