On Thu Mar 23, 2017 at 07:50:34PM -0400, Richard Hipp wrote:
> The second beta release for SQLite 3.18.0 is now available on the website:
> 
>    https://www.sqlite.org/download.html

I see the following issue:

    Program terminated with signal SIGSEGV, Segmentation fault.
    #0  sqlite3VdbeExec (p=p@entry=0x9ca2558) at sqlite3.c:83010
    83010     pCrsr = pC->uc.pCursor;
    (gdb) print pC
    $1 = (VdbeCursor *) 0x0
    (gdb) backtrace
    #0  sqlite3VdbeExec (p=p@entry=0x9ca2558) at sqlite3.c:83010
    #1  0xb71b56a2 in sqlite3Step (p=0x9ca2558) at sqlite3.c:76605
    #2  sqlite3_step (pStmt=<optimized out>) at sqlite3.c:11130
    #3  0xb713069b in sqlite_st_execute (sth=0xa2b1dc0, imp_sth=0xa331238)
        at dbdimp.c:1038
    #4  0xb7121b1d in XS_DBD__SQLite__st_execute (cv=0x98f34d8) at 
./SQLite.xsi:614
    #5  0xb7254e8d in XS_DBI_dispatch ()
       from 
/home/mark/src/bif/.direnv/perl5/lib/perl5/i686-linux/auto/DBI/DBI.so
    #6  0x080edcb7 in Perl_pp_entersub ()
    #7  0x080e7393 in Perl_runops_standard ()
    #8  0x08083f12 in perl_run ()
    #9  0x0806227d in main ()

The segfault seems to occur during COMMIT.

Versions 3.16 and 3.17 show the same behaviour but 3.13 does not
(changing nothing else other than sqlite3.[ch] and sqlite3ext.h).

Mark
-- 
Mark Lawrence
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to