Page 1 of 1

CoreLab.MySql.ah.a.mysql_get_server_info(IntPtr A_0)

Posted: Fri 12 Sep 2008 16:34
by DwightFowler
I've got a product in the field and it is throwing a System.AccessViolation exception. I'm having a hard time interpreting what is causing the problem. Can anyone help decipher this error stack?

Code: Select all

System.AccessViolationException
Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben.
Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist.
Stack Trace:
bei CoreLab.MySql.ah.a.mysql_get_server_info(IntPtr A_0)
bei CoreLab.MySql.at.l()
bei CoreLab.MySql.MySqlInternalConnection.get_ServerVersionNormalized()
bei CoreLab.MySql.MySqlConnection.h()
bei CoreLab.MySql.MySqlConnection.Open()
bei Quest.Toad.Db.Connection.OpenConnection(IDbConnection connection)
bei Quest.Toad.MySQL.MySQLConnection.OpenConnection(IDbConnection
connection)

Posted: Mon 15 Sep 2008 10:47
by Shalex
Please send me (alexsh at devart.com) your libmysql.dll or provide its version to us. Does this error occur permanently or from time to time?

Posted: Wed 24 Sep 2008 18:20
by DwightFowler
Alex,

I'm tracking down the version of the libmysql.dll for you. I will send it to you as soon as I can.

Posted: Tue 30 Sep 2008 13:35
by Shalex
The problem is fixed. Look forward to the next build of MyDirect .NET.

Posted: Tue 30 Sep 2008 14:12
by DwightFowler
Can you give us any info on what was happening?

Posted: Wed 01 Oct 2008 08:33
by Shalex
It was an incorrect usage of our provider in the client mode in OS Vista. The System.AccessViolation exception was arisen when invoking the mysql_get_server_info(IntPtr A_0) method from the libmysql.dll library. The next buld of MyDirect .NET will be available in 7 days.

Access violation reappears

Posted: Wed 29 Oct 2008 19:25
by DwightFowler
Alex,

I have a new customer that is using version 4.85.36 of MyDirect on WinXP Home 32 bit. He is getting the same error stack:

Code: Select all

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Stack trace:

   at CoreLab.MySql.ah.a.mysql_get_server_info(IntPtr A_0)
   at CoreLab.MySql.at.l()
   at CoreLab.MySql.MySqlInternalConnection.get_ServerVersionNormalized()
   at CoreLab.MySql.MySqlConnection.h()
   at CoreLab.MySql.MySqlConnection.Open()
Is there anything I can do to help track this down?

Posted: Thu 30 Oct 2008 09:01
by Shalex
dotConnect for MySQL beta version 5.00.1 Trial Edition does not have this problem and can be downloaded from our site now. The final release of dotConnect for MySQL will be available soon.