We've gotten two separate reports of PCSCTUN_DEBUG not working on Ubuntu. I got the opportunity to test it out today, and it turns out that Ubuntu's Glib has some different log settings than we are used to. To get it to work you have to also set G_MESSAGES_DEBUG=all. I think we can fix this inside pcsctun though.
Fixed in r26804.
Tester can also check that G_MESSAGES_DEBUG=pcsctun works.
Getting a crash of pcsctun on Windows when it terminates. Assuming it is because of this bug.
Also crashes on Linux.
(In reply to comment #3)
> Also crashes on Linux.
Nm. It was just glib that likes to do SIGTRAP on fatal errors. So the crash is only on Windows.
Idiot upstream managed to break static linking on Windows:
I think I can easily fix it though.
Fixed in r26922.
Reopening a random pcsctun bug - see bug 4593 for details.
*** Bug 4593 has been marked as a duplicate of this bug. ***
Fixed again in r27100.
Tested from Windows 7 with an exported smart card. Could not reproduce the crash.
Connecting to an Ubuntu 13.04 server and running:
PCSCTUN_DEBUG=1 pkcs15-tool --list-certificates
gives debug output, as does:
G_MESSAGES_DEBUG=pcsctun pkcs15-tool --list-certificates
Works as expected, so closing.