/ View Ticket
Login
2011-12-22
02:11 Fixed ticket [ac0ff496]: Database corruption due to integer overflow with SQLITE_DIRECT_OVERFLOW_READ plus 2 other changes (artifact: 60b70487 user: drh)
2011-12-21
23:38
Cherry-pick the SQLITE_DIRECT_OVERFLOW_READ fix for ticket [ac0ff496b7e] of changes [c5256b59ad] and [c723e3e18a] into the nx-devkit branch. (check-in: 42f31f19 user: drh tags: nx-devkit)
18:04
Fix other problems where 32-bit integer overflow may cause a problem. Two that require an improbably large sub-journal and two in test harness code. Ticket [ac0ff496b7e2] (check-in: c723e3e1 user: dan tags: trunk)
17:00
Avoid 32-bit overflow when calculating the byte offset of an overflow page in SQLITE_DIRECT_OVERFLOW_READ code. Fix for [ac0ff496b7]. (check-in: c5256b59 user: dan tags: trunk)
16:25 New ticket [ac0ff496] Database corruption due to integer overflow with SQLITE_DIRECT_OVERFLOW_READ. (artifact: 09f179ff user: drh)

Ticket Hash: ac0ff496b7e21147e9985332256389074bc7722d
Title: Database corruption due to integer overflow with SQLITE_DIRECT_OVERFLOW_READ
Status: Fixed Type: Code_Defect
Severity: Severe Priority: Immediate
Subsystem: Unknown Resolution: Fixed
Last Modified: 2011-12-22 02:11:23
Version Found In: 3.7.9
Description:
When the (non-standard) compile-time option SQLITE_DIRECT_OVERFLOW_READ is used, a 32-bit integer overflow at /artifact/80ea65224512?ln=3982 will likely cause the database to be reported as corrupt. The database is not really harmed by this, but attempts to read the database will be unsuccessful.

This bug has existed since the SQLITE_DIRECT_OVERFLOW_READ option was added on 2011-10-08 by check-in [2ab14a8467278571].