[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]

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-20 22:09:57.000000000 -0400
+++ shadow/76494.tmp.27107	2005-10-20 22:11:03.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 76494
 Product: Mono: Class Libraries
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: Gentoo 2.6.11 (crappy mobile celeron) / mono 1.1.9.2
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: 008 One day
 Priority: Minor
 Component: Sys.Data
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: tekhedd at byteheaven.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -110,6 +110,17 @@
 Perhaps related to nptl?
 
 ------- Additional Comments From tekhedd at byteheaven.net  2005-10-20 22:09 -------
 Created an attachment (id=15954)
 Changes the parameter to sqlite3_bind_text so that sqlite won't free the string parameter
 
+
+------- Additional Comments From tekhedd at byteheaven.net  2005-10-20 22:11 -------
+I think I have located the problem. String parameters are being freed
+by the sqlite3 libraries when it is done with them. if I change this
+behavior (by specifying the SQLITE_STATIC magic value in the call to
+sqlite3_bind_text0, the errors go away.
+
+I am not an expert, but this feels right. The previous patch is
+against svn, and creates magic enum variables (which may not match
+mono style, but it gets the poitn across). In any case, this is the
+proverbial one-line fix, so you probably don't need a patch anyway. :)