Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
3.0.9
-
None
-
Server: Windows 7 SP1 64-bit, MariaDB 10.3.9
Client: Windows 7 SP1 64-bit, .NET 4.6.1
Description
Executing
SELECT 1;
|
SELECT 1;
|
via .NET ExecuteNonQueryAsync() throws a System.AccessViolationException instead of e.g. an OdbcException:
Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
|
at System.Data.Common.UnsafeNativeMethods.SQLMoreResults(OdbcStatementHandle StatementHandle)
|
at System.Data.Odbc.OdbcStatementHandle.MoreResults()
|
at System.Data.Odbc.OdbcDataReader.NextResult(Boolean disposing, Boolean allresults)
|
at System.Data.Odbc.OdbcDataReader.Close(Boolean disposing)
|
at System.Data.Odbc.OdbcDataReader.Dispose(Boolean disposing)
|
at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader, Object[] methodArguments, SQL_API odbcApiMethod)
|
at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader)
|
at System.Data.Odbc.OdbcCommand.ExecuteNonQuery()
|
at System.Data.Common.DbCommand.ExecuteNonQueryAsync(CancellationToken cancellationToken)
|
at System.Data.Common.DbCommand.ExecuteNonQueryAsync()
|
|
Trace attached.