[Mono-bugs] [Bug 76494][Min] Changed - Mono.Data.SqliteClient Memory corruption when reusing connection after DELETE with named parameters

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Oct 21 00:07:24 EDT 2005

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by tekhedd at byteheaven.net.


--- shadow/76494	2005-10-20 22:56:41.000000000 -0400
+++ shadow/76494.tmp.32540	2005-10-21 00:07:24.000000000 -0400
@@ -129,6 +129,14 @@
 OK, maybe I've just been staring at this for too long. 
 I am still seeing memory problems, but now the program runs through
 quit ea few more queries first. So perhaps that was just a red herring
 and this isn't really an sqlite wrapper problem. (Although it does
 look like that patch actually fixes something.)
+------- Additional Comments From tekhedd at byteheaven.net  2005-10-21 00:07 -------
+I'm not crazy after all. The code does not marshal the return value
+from Sqlite.sqlite3_bind_parameter_name, resulting in a double-free of
+that string. 
+My new crash is unrelated. (BeginTransaction(IsolationLevel always
+returns null!)

More information about the mono-bugs mailing list