This bug reproduces to the latest Sqlite release (3.8.8.3). The log from the bug: sqlite> .t file sqlite> .t Usage: .trace FILE|off sqlite> .d PRAGMA foreign_keys=OFF; BEGIN TRANSACTION; Segmentation fault
I also found another bug with the same root cause: sqlite> .t file sqlite> .t Usage: .trace FILE|off sqlite> .t *** Error in `.libs/lt-sqlite3': double free or corruption (top): 0x00000000024ab340 *** Aborted -----Original Message----- From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Carabas, Costin Sent: Friday, March 6, 2015 10:39 AM To: sqlite-users at mailinglists.sqlite.org Subject: [sqlite] Sqlite3 Bug Found Hello, I was working on version 3.8.8.2 of sqlite3 and I found a bug that is trace related. It can be reproduced in 3 steps: 1. ".t log" - opens log for tracing 2. ".t" - no argument. Closes the file descriptor that was previously opened (Problem) 3. ".d" - dumps into the file that was previously closed. = > Segmentation Fault Where: .t = .trace .d = .debug Best Regards, Costin _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
