On 2012.07.09 09:48, sebasti...@gmx-topmail.de wrote: > Setting the debug level to 4 had no impact on the logging behavior of pcscd.
This is unfortunate, as we are missing a lot of information with regards to what libusbx is doing if level 4/debug is not in use. Especially, we still have no idea what may have been going on at the time of the new crash you experienced, which makes it difficult to know where we should look. > Only when started in foreground, pcscd provides detailed debug information of > libusb in the console, but does not write them to the log file. I still think we will need to get some debug output to be recorded one way or another. If pcscd only picks up the stderr output of libusbx with the --foreground option, this may require patching pcscd to also do the same when running as a daemon. Or you could patch usbi_log_v() in core.c to send its logging output to a file instead of stderr, and recompile the library. Regards, /Pete ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
