From: Shawn Willden (shawn-musclewillden.org)
Date: Mon Mar 13 2006 - 08:58:27 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I haven't nailed down exactly what's going on, in spite of several focused
hours of trying, but I have found a scenario that causes some sort of
deadlock. What happens is the client sends a message to pcscd and then
blocks forever waiting for the response, even though pcscd is up and running.
It most often happens when the client calls SCardEndTransaction.

The situation that creates it is when I have two applications that are both
watching for card insertion and both begin heavy card communications as soon
as the card is inserted. Both apps connect to the card in shared mode, and
both are wrapping all card communications in transactions. Well, I'm pretty
sure everything is inside a transaction -- this code is complex and not
originally mine, so I can't absolutely guarantee it.

In any case, I'd appreciate any suggestions from anyone who's familiar with
the code. I'm strongly suspecting a pcscd bug, and I'll track it down and
fix it if so, but I could use suggestions as to where to start looking, if
you have any.

Thanks,

        Shawn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBEFYiX6d8WxFy/CWcRAtKFAJ0YK7nolhRhmicPfU2Fe/3V1qe92wCfe+pu
ffqmy404d33OV2VsyZYuWhg=
=GSb6
-----END PGP SIGNATURE-----

_______________________________________________
Muscle mailing list
Musclelists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]