Hi,
We found a crash bug in sqlite. Here’s the POC:
—
CREATE VIRTUAL TABLE v0 USING fts4 ( v1 , v2 , v3 , v4 ) ;
INSERT INTO v0 ( v1 ) VALUES ( 10 ) ,( 10 ) ;
CREATE TABLE v5 ( v6 UNIQUE NOT NULL PRIMARY KEY UNIQUE ) ;
INSERT INTO v5 ( v6 , v6 ) SELECT nullif ( DISTINCT zeroblob ( julianday () ) ,
v3 ) , v1 + 10 FROM v0 ;
—
Here’s the backtrace:
—
#0 __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:69
#1 0x0000000000661302 in sqlite3BlobCompare (pB1=<optimized out>,
pB2=<optimized out>) at sqlite3.c:81071
#2 0x000000000063d703 in sqlite3VdbeMemAboutToChange (pVdbe=<optimized out>,
pMem=<optimized out>) at sqlite3.c:75954
#3 0x0000000000626b49 in sqlite3VdbeExec (p=<optimized out>) at sqlite3.c:85159
#4 0x00000000004b076b in sqlite3Step (p=<optimized out>) at sqlite3.c:82730
#5 sqlite3_step (pStmt=<optimized out>) at sqlite3.c:17259
#6 0x0000000000484686 in exec_prepared_stmt (pArg=0x7fff5a635990,
pStmt=0x1956950) at shell.c:11383
#7 0x0000000000442eea in shell_exec (pArg=<optimized out>, zSql=<optimized
out>, pzErrMsg=<optimized out>) at shell.c:11688
#8 0x0000000000487ad8 in runOneSqlLine (p=0x7fff5a635990,
zSql=0x193b480 "CREATE VIRTUAL TABLE v0 USING fts4 ( v1 , v2 , v3 , v4 ) ;
INSERT INTO v0 ( v1 ) VALUES ( 10 ) ,( 10 ) ; CREATE TABLE v5 ( v6 UNIQUE NOT
NULL PRIMARY KEY UNIQUE ) ; INSERT INTO v5 ( v6 , v6 ) SELECT n"...,
in=0x7f6b75fe38e0 <_IO_2_1_stdin_>, startline=1) at shell.c:18269
#9 0x0000000000449a9f in process_input (p=<optimized out>) at shell.c:18369
#10 0x0000000000418fb2 in main (argc=<optimized out>, argv=<optimized out>) at
shell.c:19135
—
The bug exists in the latest development code.
Yongheng & Rui
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
