[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:29: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.

http://bugzilla.ximian.com/show_bug.cgi?id=76494

--- shadow/76494	2005-10-21 00:07:24.000000000 -0400
+++ shadow/76494.tmp.32692	2005-10-21 00:29:24.000000000 -0400
@@ -137,6 +137,17 @@
 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!)
+
+------- Additional Comments From tekhedd at byteheaven.net  2005-10-21 00:29 -------
+To follow: a patch that accomplishes 3 things:
+
+  - Tells sqlite3 not to free the passed string parameter data
+  - marshals the returned string when getting parameter names
+  - BeginTransaction throws NotImplementeException instead of returning
+    null. (It's not supposed to return null, is it?)
+
+"It's just a small thing, but they say that it could destroy the
+universe."  --deep thought


More information about the mono-bugs mailing list