Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Changes In Branch robust-against-damaged-db Excluding Merge-Ins
This is equivalent to a diff from 147a9429a5 to 585c94db09
2018-10-30
| ||
15:20 | Improvements to the -fsanitize=fuzzer based database file fuzzer. (Cherrypick from the rubust-against-damaged-db branch.) (check-in: 3cc01a0eaf user: drh tags: trunk) | |
13:19 | Enable sqlite3_deserialize() in the CLI. The --deserialize option associated with opening a new database cause the database file to be read into memory and accessed using the sqlite3_deserialize() API. This simplifies running tests on a database without risk of modifying the file on disk. (check-in: 5e0129ee9a user: drh tags: trunk) | |
00:06 | Improvements to the -fsanitize=fuzzer based database file fuzzer. (Closed-Leaf check-in: 585c94db09 user: drh tags: robust-against-damaged-db) | |
00:06 | In the VACUUM command, defer setting writable_schema until after it has been determined that the schema is not corrupt. (check-in: 3afec26014 user: drh tags: robust-against-damaged-db) | |
2018-10-29
| ||
21:01 | Fix a potential assertion fault that can occur while trying to DROP a table from a corrupted database file. (check-in: 147a9429a5 user: drh tags: trunk) | |
18:33 | Fix minor memory leak in the dbstat extension that can occur following an attempt to analyze a corrupt database file. (check-in: cb874fd873 user: drh tags: trunk) | |
Changes to src/vacuum.c.
Changes to test/dbfuzz2.c.