SQLite User Forum

segmentation fault occured
Login
Chronological

segmentation fault occured

(1) By youngjooko (y0108009) on 2021-05-24 12:48:16 [link] [source]

During using SQLite, segmentation fault occured.

I sent

CREATE TABLE v0 ( v2 INTEGER AS( ( 'x' IN ( 0 , 0 , 10 , NOT ( v1 ) IS NULL , 1 , 10 , 10 , 1 , 9223372036854775807 ) ) ) UNIQUE , v1 UNIQUE ) ; CREATE VIEW v3 AS SELECT DISTINCT * , v1 , sum ( DISTINCT v2 ) FROM v0 GROUP BY v2 , v2 ; SELECT DISTINCT ( random () % 10 ) FROM v3 NATURAL JOIN v3 JOIN v3 , v0 , v3;

to SQLite then the SQLite crashed.

The version is 3.36.

(2) By Richard Hipp (drh) on 2021-05-24 14:13:11 in reply to 1 [link] [source]

The version is 3.36.

"Version 3.36.0" can refer to any of 274 different check-ins. Which of these specifically are you using. I ask because I cannot seem to recreate your problem.

(3) By youngjooko (y0108009) on 2021-05-25 04:53:28 in reply to 2 [link] [source]

The git log shows that the last commit ID is 252d582a35d4e24fbd9311ee98b18730543d9622.

Thank you for your attention.

(4) By Richard Hipp (drh) on 2021-05-25 12:43:38 in reply to 3 [link] [source]

SQLite does not use Git. SQLite uses Fossil. The Fossil check-in that corresponds to Git 252d582a35d4e24f is c22e47c77a35ebcd. That check-in occurred 48 days ago on 2021-04-07. The bug you report was fixed on the following day (2021-04-08) by check-in 0e4789860b81c31d.

(5) By Richard Hipp (drh) on 2021-05-25 13:27:46 in reply to 3 [source]

This graph shows an abbreviated sequence of check-ins starting with the first check-in labeled as "3.36.0" and ending with the latest check-in at the time this problem was reported. The sequence shows:

  1. Where the bug was fixed
  2. The check-in against which the bug was reported (highlighted)
  3. Where the bug was introduced

Snarky rhetorical question: How would you display this kind of information using Git?