What I'm testing is my code. I want to be sure the code is going to work. A crash is a primary indication that it won't. That's information, not just an annoyance.
On Sat, Sep 30, 2017 at 5:37 PM, Joseph L. Casale <jcas...@activenetwerx.com > wrote: > -----Original Message----- > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On > Behalf Of Kevin O'Gorman > Sent: Saturday, September 30, 2017 3:55 PM > To: sqlite-users <sqlite-users@mailinglists.sqlite.org> > Subject: [sqlite] Seg fault with core dump. How to explore? > > > Here's my prime suspect: I'm using WAL, and the journal is 543 MB. > > Do you really need any reliability at all for a test? Who cares if the > power goes out or the program crashes? If this is a test, you will simply > restart it and the data is irrelevant so why impede any potential > performance for data integrity? > > Try setting the journal_mode off... > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- word of the year: *kakistocracy* _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
