John Chen wrote: > Tim, I attache the usb debug trace and USB_Trace here. Yes, I did get > a timeout, but if you look at USBTrace.txt, it have the following: > > [libusb_get_next_timeout] no URB with timeout or all handled by OS; no > timeout! > do you need what it means?
It looks like you are running multiple simultaneous event loops. Is that correct? You don't need to do that. You can see how the log output is garbled, apparently because the log output is intermixed with another thread writing at the exact same time. My best guess is that you have some kind of multithreading problem, but there's not much we can do without seeing the whole code, and I'm not sure you really want to do that. You need to think about what order things are happening, remembering that asynchronous operations will always arrive at the most inconvenient time. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ 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
