| Subject | how debug a memory corruption exception |
|---|---|
| Author | |
| Post date | 2014-03-12T14:09:15Z |
hi, i'm using the .net provider with the last embedded fb version on a x64 windows 7 machine.
i have an application always active that abaout every minute will connect to the db, 1/2 times a day it crashes when it tries to open the connection, this is the relevant stack trace of the exception:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at FB_1236665269_Class.isc_attach_database(IntPtr[] statusVector, Int16 dbNameLength, Byte[] dbName, Int32& dbHandle, Int16 parmBufferLength, Byte[] parmBuffer)
i see in an old fb thread in the forum the suggestion to download the Debug Kit to give you same useful informations to find the bug that cause this kind of exception but the link with the description of how use the debug kit was broken.
now i'm using the debug kit files in my app so i want know what i must do the next time that my app will crash to send you same info (i'm a .NET developer and i don't know how debug a native application)
i have an application always active that abaout every minute will connect to the db, 1/2 times a day it crashes when it tries to open the connection, this is the relevant stack trace of the exception:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at FB_1236665269_Class.isc_attach_database(IntPtr[] statusVector, Int16 dbNameLength, Byte[] dbName, Int32& dbHandle, Int16 parmBufferLength, Byte[] parmBuffer)
i see in an old fb thread in the forum the suggestion to download the Debug Kit to give you same useful informations to find the bug that cause this kind of exception but the link with the description of how use the debug kit was broken.
now i'm using the debug kit files in my app so i want know what i must do the next time that my app will crash to send you same info (i'm a .NET developer and i don't know how debug a native application)