Issue Details (XML | Word | Printable)

Key: ODBC-137
Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Critical Critical
Assignee: Alexander Potapchenko
Reporter: Roberto Carlos da Silva
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ODBC Driver

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

Created: 31/Jan/12 01:49 PM   Updated: 31/May/12 03:27 PM
Component/s: None
Affects Version/s: 2.0 Beta, 2.0 RC1, 2.0 RC2 , 2.0, 2.0.1, 2.1 Beta
Fix Version/s: 2.0.1

File Attachments: 1. Zip Archive TestThreadSafe.zip (444 kB)

Environment: Windows 7, Firebird ODBC, visual studio .NET


 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Roberto Carlos da Silva made changes - 31/Jan/12 01:51 PM
Field Original Value New Value
Attachment TestThreadSafe.zip [ 12095 ]
Alexander Potapchenko made changes - 21/Mar/12 10:49 AM
Status Open [ 1 ] Resolved [ 5 ]
Fix Version/s 2.0.1 [ 10430 ]
Resolution Won't Fix [ 2 ]
Alexander Potapchenko made changes - 31/May/12 03:27 PM
Status Resolved [ 5 ] Closed [ 6 ]