As a matter of fact sqlite3_reset and sqlite3_finalize also segfault if invoked on that prepared sqlite3_stmt, so there's something seriously screwed up, but not immediately obvious what exactly since the previous sqlite3_column_* and sqlite3_step calls worked just fine to get all 9 rows that are supposed to be returned...
Thanks! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 [EMAIL PROTECTED] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. -----Original Message----- From: Boris Popov [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 28, 2006 10:16 PM To: sqlite-users@sqlite.org Subject: [sqlite] sqlite3_step crash? Hmm, I have a fairly specific scenario here where after fetching values from all the rows in the result set calling sqlite3_step segfaults instead of returning SQLITE_DONE. I'm at a loss as to how I could extract a little more info to help figure this out, so any pointers would be greatly appreciated. Thanks! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 [EMAIL PROTECTED] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you.
smime.p7s
Description: S/MIME cryptographic signature
