| Bug #15291 | Memory leak in MyODBC utility library | ||
|---|---|---|---|
| Submitted: | 28 Nov 2005 16:16 | Modified: | 18 May 2007 2:20 |
| Reporter: | Bogdan Degtyariov | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S2 (Serious) |
| Version: | 3.51.12 | OS: | Windows (Windows XP) |
| Assigned to: | Bogdan Degtyariov | CPU Architecture: | Any |
[29 Nov 2005 16:24]
Jorge del Conde
I was able to reproduce this using attatching a myodbc process to bounds-checker
[18 May 2007 2:20]
Jim Winstead
No need to document this.
[3 Sep 2007 14:22]
Tonci Grgin
Bug#11381 was marked as duplicate of this one.
Description: MyODBC assigns a newly allocated memory address to a not-null pointer during the parsing of the connection string. How to repeat: Just call SQLDriverConnect function with the following connection string "DRIVER={MySQL ODBC 3.51 Driver};SERVER=localhost;Database=test;Uid=root;Pwd=;Option=4;"