Bug #40316 | calling SQLDriverConnect() with no output buffer will crash if not prompting | ||
---|---|---|---|
Submitted: | 24 Oct 2008 18:42 | Modified: | 10 Nov 2008 15:24 |
Reporter: | Jess Balint | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | Any |
Assigned to: | Jess Balint | CPU Architecture: | Any |
[24 Oct 2008 18:42]
Jess Balint
[31 Oct 2008 18:12]
Jess Balint
This bug was a result of the change in bug#38949 and as a result is not included in any official release. Fix pushed as rev 807, will be included in 5.1.6.
[10 Nov 2008 15:24]
Tony Bedford
An entry was added to the 5.1.6 changelog: Calling SQLDriverConnect() with a NULL pointer for the output buffer caused a crash if SQL_DRIVER_NOPROMPT was also specified: SQLDriverConnect(dbc, NULL, "DSN=myodbc5", SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT)