Re: [sqlite] Seg fault with core dump. How to explore?

-Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Kevin O'Gorman Sent: Saturday, September 30, 2017 6:40 PM To: SQLite mailing list Subject: Re: [sqlite] Seg fault with core dump. How to explore?

Re: [sqlite] Seg fault with core dump. How to explore?

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 wrote: > -Original Message- > From:

Re: [sqlite] Seg fault with core dump. How to explore?

I'm using the standard shim, because I've been using it forever and first head of APSW just a few days ago. I'm guessing it should be pretty easy to switch because I'm not doing anything weird. All my columns are INTEGER or CHAR, there are not even any foreign keys, although one of the two main

Re: [sqlite] Seg fault with core dump. How to explore?

-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 Subject: [sqlite] Seg fault with core dump. How to explore? > Here's

Re: [sqlite] Seg fault with core dump. How to explore?

On 30 Sep 2017, at 10:54pm, Kevin O'Gorman wrote: > Here's my prime suspect: I'm using WAL, and the journal is 543 MB. I > hadn't given it much thought, but could this be more than the software > really wants to deal with? No SQLite. Possibly something else you’re

[sqlite] Seg fault with core dump. How to explore?

I'm testing new code, and my latest trial run ended with a segmentation fault after about 5 hours. I'm running Python 3.5 and its standard sqlite3 module On Xubuntu 16.04.3 LTS. The code is short -- about 300 lines. This particular program is merging two databases. The result has reached 25 GB,