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

2017-10-01 Thread Simon Slavin
On 2 Oct 2017, at 5:33am, Kevin O'Gorman wrote: > What such things always say "segementation fault (core dumped)" and the > name of the program. Try standard investation for any Python program which gives a segmentation fault. Waht does faulthandler say ?

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

2017-10-01 Thread Kevin O'Gorman
On Sat, Sep 30, 2017 at 11:41 PM, Clemens Ladisch wrote: > Kevin O'Gorman wrote: > > my latest trial run ended with a segmentation fault > > Really a segmentation fault? What is the error message? > What such things always say "segementation fault (core dumped)" and the

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

2017-10-01 Thread Clemens Ladisch
Kevin O'Gorman wrote: > my latest trial run ended with a segmentation fault Really a segmentation fault? What is the error message? > This particular program is merging two databases. The result has reached > 25 GB, roughly 1/3 of what I expect of the final result (over 100M rows). > The

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

2017-09-30 Thread Joseph L. Casale
-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 <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sqlite] Seg fault with core dump. How to e

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

2017-09-30 Thread Kevin O'Gorman
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? > &g

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

2017-09-30 Thread Kevin O'Gorman
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?

2017-09-30 Thread Joseph L. Casale
-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? &g

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

2017-09-30 Thread Simon Slavin
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?

2017-09-30 Thread Kevin O'Gorman
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,