Thanks Simon. I should mention I was testing the version of SQLAlchemy 2.0.38+ds1. It's possible it has a newer test that exercises the failing part of SQLite3. This testing is for a backport to the Ubuntu Cloud Archive for the latest version of OpenStack. I did some manual `git bisect` between SQLite3-3.45.2 and 3.45.3 and I believe the first "good" git commit is 74851f66811854c772a9b2d0a13f1e9e82b69c25. Before that commit running:
python -m pytest -q \ ~/sqlalchemy-2.0.38+ds1/test/orm/inheritance/test_assorted_poly.py::\ MultiOfTypeContainsEagerTest_joined::test_big_query \ --db default produces the segfault. This commit appears to contain the fix. For reference, the reason I'm doing this testing is to solve this build failure for SQLAlchemy backport: https://launchpad.net/~ubuntu-cloud- archive/+archive/ubuntu/flamingo-staging/+build/30923593 Also please let me know if what I'm describing should be a new bug report. It felt similar to the initial submission though I'm not positive it's the same segfault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2087772 Title: crash (segfault) in libsqlite3 running multi-join query To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2087772/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
