If you recompile sqlite3 with -DSQLITE_DEBUG=1, run sqlite3 in a
debugger, and set a breakpoint on sqlite3Corrupt you can get
a stack trace showing what led up to SQLITE_CORRUPT.
But although this will show you roughly where the file is corrupt,
it probably won't help you with why.
If your OS is repeatably ceasing while running your app, you've
probably got a hardware problem. Windows or not, this shouldn't happen.
--- Andrew Finkenstadt <[EMAIL PROTECTED]> wrote:
> 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.
____________________________________________________________________________________
Got a little couch potato?
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
