Rousseau wrote:
>>> Another idea is a bug in ELDK. >> That I could buy, but why would then the old pcsc-lite-1.3.something work ?? >> The change in behavior came through the upgrade of the pcsc-lite part of >> the system... > I propose to check the different versions of pcsc-lite to know in > which version the problem was introduced. That's a lot of compiling to do, will take much time... have to push that question upwards (middle-management) I think :-/ > Then you fine tune your research using svn-bisect [1]. > I never used svn-bisect and I was not aware of its existence 10 > minutes ago. So I don't know if it is really adapted. > [1] http://search.cpan.org/~infinoid/App-SVN-Bisect-1.1/bin/svn-bisect That was a new one, sounds interesting !! To more describe the behavior, when my application hangs in it's attempt to communicate with the deamon, it apparently does it in a select according to the strace. And I supposed that nothing went forth and said anything either way. But when I kill my app with a Ctrl-C it takes the down with it pcscd !! And I pretty sure that isn't a deliberate part of my code, and I'm also pretty sure that it didn't manage to kill the 'pcscd' when I'm running it with '-f' ! So there is some kind of communication going on between here. A cut from the last part of the log: pcscd: ifdhandler.c:483:IFDHGetCapabilities() Reader supports 1 slot(s) pcscd: hotplug_libusb.c:412:HPEstablishUSBNotifications() Driver ifd-ccid.bundle does not support IFD_GENERATE_HOTPLUG. Using active polling instead. pcscd: hotplug_libusb.c:421:HPEstablishUSBNotifications() Polling forced every 1 second(s) pcscd: ifdhandler.c:1135:IFDHPowerICC() action: PowerUp, usb:076b/6622:libusb:002:002 (lun: 0) pcscd: Card ATR: 3B 98 96 81 11 FE 53 41 4D 20 76 33 2E 36 42 ! And here I give my app (not the 'pcscd') the Ctrl-C... pcscd: pcscdaemon.c:649:signal_trap() Received signal: 2 pcscd: pcscdaemon.c:654:signal_trap() Preparing for suicide pcscd: hotplug_libusb.c:381:HPRescanUsbBus() Hotplug stopped pcscd: readerfactory.c:1288:RFCleanupReaders() entering cleaning function pcscd: readerfactory.c:1297:RFCleanupReaders() Stopping reader: OmniKey CardMan 6121 00 00 pcscd: eventhandler.c:170:EHDestroyEventHandler() Stomping thread. pcscd: ifdhandler.c:395:IFDHGetCapabilities() tag: 0xFB1, usb:076b/6622:libusb:002:002 (lun: 0) pcscd: eventhandler.c:185:EHDestroyEventHandler() Waiting polling thread pcscd: eventhandler.c:521:EHStatusHandlerThread() Die pcscd: eventhandler.c:209:EHDestroyEventHandler() Thread stomped. pcscd: readerfactory.c:1026:RFUnInitializeReader() Attempting shutdown of OmniKey CardMan 6121 00 pcscd: ifdhandler.c:296:IFDHCloseChannel() usb:076b/6622:libusb:002:002 (lun: 0) pcscd: readerfactory.c:886:RFUnloadReader() Unloading reader driver. pcscd: winscard_svc.c:127:ContextsDeinitialize() remaining threads: 0 pcscd: pcscdaemon.c:601:at_exit() cleaning /var/run Is there any higher log-level to kick in on the pcscd ?? I would very much like to know the flow of the signals and who is waiting for what.. -- /Ivar The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately. _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
