Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempted to read or write protected memory. This is often an indication that other memory is corrupt [ODBC137] #134

Closed
firebird-automations opened this issue Jan 31, 2012 · 5 comments

Comments

@firebird-automations
Copy link

Submitted by: Roberto Carlos da Silva (robertosistemas)

Attachments:
TestThreadSafe.zip

some errors reported:

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

(2) ERROR [08S01] [ODBC Firebird Driver][Firebird]Error reading data from the connection.

(3) ERROR [HY000] [ODBC Firebird Driver][Firebird]request synchronization error.

The read error occurs when the option is not used thread-safe.
As a suggestion, it would be nice if the thread-safe option was enabled by default in the drive.
not passing the attribute SAFETHREAD = Y in the connection string.
because in most ODBC drivers are already thread-safe without any attribute.

@firebird-automations
Copy link
Author

Commented by: Roberto Carlos da Silva (robertosistemas)

Project attached for testing

some errors reported:

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

(2) ERROR [08S01] [ODBC Firebird Driver][Firebird]Error reading data from the connection.

(3) ERROR [HY000] [ODBC Firebird Driver][Firebird]request synchronization error.

The read error occurs when the option is not used thread-safe.
As a suggestion, it would be nice if the thread-safe option was enabled by default in the drive.
not passing the attribute SAFETHREAD = Y in the connection string.
because in most ODBC drivers are already thread-safe without any attribute.

@firebird-automations
Copy link
Author

Modified by: Roberto Carlos da Silva (robertosistemas)

Attachment: TestThreadSafe.zip [ 12095 ]

@firebird-automations
Copy link
Author

Commented by: @alexpotapchenko

Roberto,
I have not understood you.
If you use the connection string: Driver={Firebird/InterBase(r) driver};dbname=localhost:c:\temp\DbTest.fdb;charset=WIN1252;uid=SYSDBA;pwd=masterkey;client=fbclient.dll" then "SAFETHREAD = Y" is the default option.
I don't see the problem, you use SAFETHREAD=N for reproduction of errors.

@firebird-automations
Copy link
Author

Modified by: @alexpotapchenko

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

Fix Version: 2.0.1 [ 10430 ]

@firebird-automations
Copy link
Author

Modified by: @alexpotapchenko

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment