Bug #36069 A SQLProcedures followed by a SQLFreeStmt causes a crash

Description:
When using the ODBC C API a crash occurs when calling SQLProcedures followed by SQLFreeStmt after successfully establishing a connection.

The version of the server that it is connecting to is 5.0.51a-community-nt

How to repeat:
1.  Establish an ODBC connection to a MySQL database through the MySQL ODBC driver.

2.  Once the connection is established make these three function calls:

    SQLHSTMT	stmt;
    int ret = SQLAllocHandle( SQL_HANDLE_STMT, database_connection, &stmt );
    ret = SQLProcedures( stmt, "", 0, "ml", 2, "ml_", 3 );
    ret = SQLFreeStmt( stmt, SQL_RESET_PARAMS );

The 'ml' database that was used in these steps had 8 procedures that began with 'ml_'.  When these commands were run against a Microsoft SQL Server database they completed successfully.

The same commands also work with version 3.51.24 of the MySQL ODBC Driver.

The C file used to reproduce the bug

Attachment: odbcbug.c (text/plain), 5.59 KiB.

One of the commands was left out in the original report, here's an update:

    SQLHSTMT	stmt;
    RETCODE	ret;    
    SQLSMALLINT size = 0; 
    ret = SQLAllocHandle( SQL_HANDLE_STMT, conn->dbc, &stmt );
    ret = SQLProcedures( stmt, "", 0, "ml", 2, "ml_", 3 );
    ret = SQLFreeStmt( stmt, SQL_RESET_PARAMS );
    ret = SQLNumResultCols( stmt, &size );

Thank you for the bug report. Do you meant a server crash or the client
application crash?. Thanks in advance.

Verified, crashes in ODBC driver.

fix + test

Attachment: bug36069.diff (application/octet-stream, text), 1.47 KiB.

I noticed that this fix did not go into 5.01.04

Would it be possible for me to get a build with this fix in it?  I am currently blocked because of this bug.

patch approved

Kevin, What is the purpose of calling SQLFreeStmt() in this way? I agree that we needed to fix this because of the crash, but otherwise I see no purpose to this calling sequence.

The ODBC function calls are generated for me so I'm not exactly sure the reason they were generated in that sequence(and can't change the sequence).  

I put together the reproducible through an ODBC trace of what was originally a java program.

Committed as rev 1114, will be released in 5.1.5.

An entry has been added to the 5.1.5 Changelog:

After having successfully established a connection, a crash occurs when calling SQLProcedures() followed by SQLFreeStmt(), using the ODBC C API.