Is there a good way/tool to determine what went wrong in a database file reporting SQLITE_CORRUPT?
The details I have so far are: machine (running Windows XP) locked up hard while executing our application. Repeatable hard-lock at a certain point. (Hard lock is defined as no mouse, no keyboard, no display update, necessitating reset button or power cycle.) I've noticed that disk drivers will lie about whether data has been truly committed to physical media in the interests of passing a benchmark faster. I suspect something is going on here.
