Found the issue: Called sqlite3_finalize after recieving a SQLITE_BUSY on on sqlite3_step, then you get a segfault and all sorts of errors, glibc related. But if I loop on SQLITE_BUSY, re-calling the sqlite3_step all is well. Can this be the correct thing to do ??? I mean I alreaded prepared the statement. Why can't it be reset of finalized if a sqlite busy is encountered ??? Ken
Ken <[EMAIL PROTECTED]> wrote: I'm getting a segfault and sigabort (sporadic) when calling sqlite3_reset. Version 3.3.9 and using sqlite3_prepare_v2... I'll retest using sqlite3_prepare. Ken
