Thanks, guys. I knew this wasn't going to be enough, I was mostly looking for suggestions as to how I should pursue the problem and it looks like I'll have to resort to writing a rusty C sample given that I haven't touched C/C++ in years. I guess I was still hoping for an "oh yea, we have a bug 123 logged and its been solved post 3.3.4 release" :)
Cheers! -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: Christian Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 29, 2006 6:40 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] sqlite3_step crash? On Wed, 29 Mar 2006 [EMAIL PROTECTED] wrote: >"Boris Popov" <[EMAIL PROTECTED]> wrote: >> >> Does this help at all? >> > >No. A stack trace, especially one without line number >information, is of no help whatsoever. I beg to differ. Any stack trace that includes malloc or free is almost certainly heap corruption. What the OP should do is: - Check for buffer overflows. - Check for multiple free()s of the same memory block. - Run the software under some memory checker. Not sure what to recommend on Windows. The problem is almost certainly in the OP's code. >D. Richard Hipp <[EMAIL PROTECTED]> Christian -- /"\ \ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL X - AGAINST MS ATTACHMENTS / \
smime.p7s
Description: S/MIME cryptographic signature
