News for hackers. Stuff that matters.

A comment on I found a bug in SQLite. Parent comment

Re:I found a bug in SQLite by zoomablemind on Sunday December 11, 2022 @04:17PM (#33947625)
>... larger than the codebase test suite

I wonder if they directly test the concurrent use?

It appears that the fix [1] of the OP bug did not lead to any addition/changes in resp. tests.

[1]:https://www.sqlite.org/src/info/15f0be8a640e7bfa

P.S. looks like Fossil still has issues with content scrolling and wrapping to screen size (mobile).

[ Parent | on HN ]
Re:I found a bug in SQLite by otoolep on Sunday December 11, 2022 @04:22PM (#33947678)
Actually, they added a unit test in a follow-on change:

https://www.sqlite.org/src/info/dc7dd2d3e50e7cc4

[ Parent | on HN ]
Re:I found a bug in SQLite by zoomablemind on Sunday December 11, 2022 @04:57PM (#33948001)
Indeed, thanks for pointing this one out.

The test seems to test a shared access in rather a serial order. I wonder if underneath this is actually running as concurrent processes?

[ Parent | on HN ]
Re:I found a bug in SQLite by otoolep on Sunday December 11, 2022 @05:15PM (#33948178)
I may not be following your point, but I don't believe the root cause of this issue was a race condition, or anything that might be related to concurrency.

The fundamental cause AFAIK was a SQLite connection was attempting to make a state transition (from one type of locking state to another) which shouldn't be allowed under certain circumstances, but the implementation didn't actually enforce this rule. So the added test really does test the root cause.

[ Parent | on HN ]