(I'm sorry if my description of the bug is not good. I tried to get as
much
information possible before sending this email).
A few days ago I encountered some weird segfaults on my django
application.
After a bit of troubleshooting I realized that the applications was
crashing on
the sqlite library.
I dumped the database and recompiled python with debugging symbols to
get the
segfaulting query. After some digging I managed to get a small
reproduction of
the segfault:
CREATE TABLE IF NOT EXISTS t (id integer NOT NULL PRIMARY KEY
AUTOINCREMENT);
INSERT INTO t VALUES(1);
SELECT a.id FROM t AS a INNER JOIN t as b ON a.id = b.id WHERE a.id IN
(1, 2, 3);
Once I got that I installed fossil and bisected the segfault to the
e130319317e76119 version, below is the output of `fossil chart`:
1 BAD 2019-02-19 20:29:05 f16d127c3b4a735a
3 BAD 2019-01-14 13:32:15 ddc3697efd61830f
5 BAD 2019-01-05 21:09:37 598d7358e7329f0d
7 BAD 2019-01-03 15:17:01 bef216dfa1456a78
8 BAD 2019-01-01 19:17:42 911342f7512145a8
9 BAD 2018-12-31 21:43:55 b57c545a384ab5d6
10 BAD 2018-12-31 20:39:37 e130319317e76119
11 GOOD 2018-12-31 17:58:05 f856676c8438dbf5 CURRENT
6 GOOD 2018-12-31 16:36:42 4678cb1044f0b4dc
4 GOOD 2018-12-24 20:00:27 3873941c4fb9aa2d
2 GOOD 2018-12-01 12:34:55 bf8c1b2b7a5960c2
I don't have experience with fossil nor sqlite3 nor SQL in general, so
I really
don't know how to add more information to this report.
Thanks in advance.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
