2012/7/28 <sebasti...@gmx-topmail.de>: > Did you have a look at the second file as well? It seems to me that there are > two different issues (different function calls).
Different backtrace but they both indicate a crash in libusbx with no (direct) relation with pcsc-lite. >> On 2012.07.28 12:06, Ludovic Rousseau wrote: >> It looks like the thread is started by the okccid driver itlself and >> not by pcscd. > If the libusbx maintainers agree with that, I'll try to contact the Omnikey > support. I am a libusbx maintainer :-) >> On 2012.07.28 12:06, Ludovic Rousseau wrote: >> You would get more detailed information by rebuilding libusbx with debug >> info. > That's too bad. As I pointed out in previous mails, the cpu load is too high > with enabled debug information. Compiled with -g compilation argument, not with --enable-debug-log With that we should see the line number and file name of the source code for libusb in the backtrace. Instead we just have: #0 0x0054d538 in libusb_submit_transfer () from /lib/i386-linux-gnu/libusb-1.0.so.0 #1 0x0054f368 in ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0 Bye -- Dr. Ludovic Rousseau ------------------------------------------------------------------------------ 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
