Ludovic Rousseau wrote: > On 13/08/06, Tony Whitmore <[EMAIL PROTECTED]> wrote: >> pcscd produces this (output from after enter is hit after entering the >> admin PIN): >> >> APDU: 00 20 00 83 08 31 32 33 34 35 36 37 38 >> T=1 -> 0 20 0 83 8 31 32 33 34 35 36 37 38 >> T=1 <- 90 0 >> SW: 90 00 >> APDU: 00 DA 00 5B 10 57 68 69 74 6D 6F 72 65 3C 3C 41 6E 74 6F 6E 79 >> T=1 -> 0 da 0 5b 10 57 68 69 74 6d 6f 72 65 3c 3c 41 6e 74 6f 6e 79 >> Segmentation fault >> >> I'd appreciate any advice as to where to look next or what further >> testing I can do. This seems likely to be a bug in in pcscd or a bug in >> the driver for my card reader. > > Try to run pcscd inside gdb to see where it crashes.
OK, I've done so. The output shown on the terminal after pressing "enter" following the admin PIN is: winscard_msg_srv.c:274:SHMProcessEventsContext() correctly processed client: 9 winscard.c:1465:SCardTransmit() Send Protocol: T=1 APDU: 00 20 00 83 08 31 32 33 34 35 36 37 38 T=1 -> 0 20 0 83 8 31 32 33 34 35 36 37 38 T=1 <- 90 0 SW: 90 00 winscard_msg_srv.c:274:SHMProcessEventsContext() correctly processed client: 9 winscard.c:1465:SCardTransmit() Send Protocol: T=1 APDU: 00 DA 00 5B 10 57 68 69 74 6D 6F 72 65 3C 3C 41 6E 74 6F 6E 79 T=1 -> 0 da 0 5b 10 57 68 69 74 6d 6f 72 65 3c 3c 41 6e 74 6f 6e 79 [New Thread -1227334736 (LWP 10746)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1227334736 (LWP 10746)] 0xffffe410 in __kernel_vsyscall () The backtrace shows: (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb7e500c1 in select () from /lib/tls/i686/cmov/libc.so.6 #2 0x0804e826 in SHMProcessEventsServer () #3 0x0804c3b2 in SVCServiceRunLoop () #4 0x0804cae3 in main () A friend has suggested that this might indicate a kernel driver bug!?! Thanks, Tony
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
