Greetings all, I'm running into a situation in where our application is crashing during a call to sqlite_backup_finish inside of btreeParseCellPtr because some of the structure is corrupted.
Both the source and destination database are using the same page sizes and I'm running everything from within a single-thread. I'd like to get clarification on one possible issue in order to determine whether this is the culprit or at least rule it out. This destination connection (which is an in-memory database) has several prepared statements, some of which are marked as busy (from sqlite3_stmt_busy) due to having step called but not reset. All of these statements are read-only (simple select statements). My question is, is it safe to have these busy statements on the destination connection while the backup happens (again, this is all single threaded so nothing happens DURING the backup process)? If not, then should sqlite3_backup_init check for this (at least in debug) and return NULL if any statements are busy? -Shaun _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
