Re: Most recent driver aborts transaction after one error

Bart Samwel wrote:

> Hiroshi Inoue wrote:
>
>> Bart Samwel wrote:
>>
>>>
>>> 2. I also encountered an access violation while exiting. The call
>>> stack was not very informative:
>>>
>>> ntdll(dot)dll!_RtlpWaitForCriticalSection(at)4() + 0x5b
>>> ntdll(dot)dll!_RtlEnterCriticalSection(at)4() + 0x46
>>> psqlodbc35w.dll!023a097e() ntdll(dot)dll!_RtlpFreeDebugInfo(at)4()
>>> + 0x57 ntdll(dot)dll!_RtlDeleteCriticalSection(at)4() + 0x78 If
>>> you want me to try this with a debug-compiled psqlodbc35w, just say
>>> the word!
>>
>>
>>
>> It looks like a thread is about to Free a Handle while another thread
>> is wating for the Handle.
>> OK please send me the mylog output.
>
>
> I've attached two mylogs: in the first, I ordered my debugger to
> continue after the access violation, in the second, I immediately
> killed the program at the point of the access violation. If you need
> more info, let me know.
>

Thanks.
Please retry the dll at
http://www.geocities.jp/inocchichichi/psqlodbc/index.html .
Check SQLGetInfo with the option SQL_DBMS_NAME or SQL_DBMS_VERSION
as well.

regards,
Hiroshi Inoue