Hello, The same behavior with 1.5.5. It seems that there is an additional problem with SCardDisconnect. I tried a workaround to loop SCardDisconnect while it returns SCARD_E_SHARING_VIOLATION. But it seems that although this error is returned, the handle is partly disconnected. Because at the second call SCARD_E_INVALID_HANDLE is returned.
It seems that you do not need multiple threads to reproduce this issue, it will also fail in one thread. I had a look at the source of pcsc-lite 1.5.3 and it looks like the problem is coming from winscard_svc.c line 657. Regards, Reinhard Steiner On Tue, Jun 29, 2010 at 4:20 PM, Ludovic Rousseau < [email protected]> wrote: > 2010/6/29 Reinhard Steiner <[email protected]>: > > Hello, > > Hello, > > > It seems that there is an issue in pcsc-lite when using transactions in > > multiple threads. It is possible to destroy a transaction of another card > > handle. > > This was tested with pcsc-lite 1.5.3 and 1.6.1. > > Can you try with pcsc-lite 1.5.5? > > > See the following pseudo calls (connect to the same smart card): > > I will try to reproduce the problem. > Thanks > > -- > Dr. Ludovic Rousseau > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle >
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
