On Mar 20, 2009, at 5:43 PM, Kim, Albert wrote: > Hi Richard, > > Thanks for your quick response! The call stack at the point when > the SQLITE_CORRUPT_BKPT occurs looks like this: > > sqlite3VdbeExec > case OP_OpenWrite: > sqlite3BtreeCursor > btreeCursor > getAndInitPage > sqlite3BtreeGetPage > sqlite3PagerAcquire > pagerAcquire > > It appears that the invalid page is operand p2 of an OpenWrite op. > It almost seems as if the prepared statement is already faulty, is > that possible? >
Can you send me the database file you are trying to access and the SQL statement that is yielding the faulty p2 operand? D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
