Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
3.2.2
-
None
-
Windows x64, .NET 8.0
Description
When executing the following code:
using System.Data.Odbc;
|
|
|
string connString = "Driver={MariaDB ODBC 3.2 Driver};Server=localhost;Port=3307;Database=DataFlow;User=root;Password=etlboxpassword;SSL Mode=None;";
|
|
|
try {
|
var dbConnection = new OdbcConnection(connString);
|
dbConnection.Open();
|
var command = dbConnection.CreateCommand();
|
command.CommandText = $"SELECT * FROM non_existing_table";
|
command.CommandTimeout = 60;
|
var reader = command.ExecuteReader();
|
} catch {
|
Console.WriteLine("Error occured");
|
}
|
a critical `System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'` exception is thrown, and the program execution is aborted (without going into the catch-block).
A "normal" System.Data.Odbc.OdbcException would be expected. The access violation is not thrown when the try/catch is removed.
Sample project is attached.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
Activity
Hi Lawrin,
thanks for getting back to me.
I observed the following behaviour.
When I run this using a debugger attached:
var dbConnection = new OdbcConnection(connString); |
dbConnection.Open();
|
var command = dbConnection.CreateCommand();
|
command.CommandText = $"SELECT * FROM non_existing_table"; |
command.CommandTimeout = 60; |
var reader = command.ExecuteReader();
|
I get a ERROR [42S02] [ma-3.2.2][11.4.2-MariaDB-ubu2404]Table 'DataFlow.non_existing_table' doesn't exist' exception, which is the expected one.
But when I run this with a debugger:
try { |
var dbConnection = new OdbcConnection(connString); |
dbConnection.Open();
|
var command = dbConnection.CreateCommand();
|
command.CommandText = $"SELECT * FROM non_existing_table"; |
command.CommandTimeout = 60; |
var reader = command.ExecuteReader();
|
} catch { |
throw; |
}
|
I get the 'System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.' exception. (Which is a "hard" exception, which will stop the execution of the .NET code immediately, without entering the catch block)
So, there seems to be a difference when running the code with or without a try/catch statement.
This error popped up in my test environment when upgrading to 11.4. I never had issues with this when using the previous MariaDb versions (10.X).
For some reason .Net still calls SQLMoreResults on the handle where query resulted in error. The driver crashed on that. The fix and the testcase have been pushed
Thank you for your report. What is interesting, is that we do have test doing select from non-existent table and all is fine with it.
Interesting what makes your test different.