Hi Ludovic, On Wed, Aug 29, 2018 at 04:11:14PM +0200, Ludovic Rousseau wrote: > Le 07/08/2018 à 13:24, Wouter Verhelst a écrit : > > I'm not sure where this is coming from, but would be happy to perform > > any required debugging steps. > > Thanks Wouter for the bug report. > > I have some questions: > - do you also have the problem if you use only 1 reader instead of 3 > (so if you do _not_ use vsmartcard)
I haven't tried this in a while, but I'll try to do so tomorrow and will let you know. > - do you start the second instance of the program immediately after > the first run? or you can run the second instance 1 second after the > first and still get the problem? I started the two instances of that program in two different terminal windows, manually. I don't know *exactly* how much time there was between both instances, but typing "./test<enter>", move mouse to other terminal, and typing again "./test<enter>" does take more than a fraction of a second; so whatever the problem may be does not require that things are changed *immediately*. > I can reproduce the behaviour you get by removing/commenting the line > 288 at > https://salsa.debian.org/rousseau/PCSC/blob/master/src/winscard.c#L288 > I am suspecting a race condition issue somewhere. But I have no idea > how to reproduce it. I don't think it is a race. Instead, I suspect some internal state corruption. Once the problem occurs once, it is easy to reproduce, but only until I restart pcscd; then I have to play with stuff again until I somehow trigger the magic incantation which makes it reappear. > What could help is to get pcscd logs when the problem occurs. But I > understand it is not easy if you don't know how to reproduce the > problem. > https://pcsclite.apdu.fr/#support I'll try anyway. -- Could you people please use IRC like normal people?!? -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008 Hacklab
