From: daves0 <not...@gi...> - 2014-12-14 21:44:57
|
Here we are almost a year later, and the "not-found" error return from libusb_cancel_transfer is not being handled. It appears efforts here were stopped because one person can cause this problem in a manner that also involves EFAULTs. In the end, however, there's still a looping bug in libusb, is there not? The loop can only be exited when a specific condition occurs / state is reached. There is a function call within the loop that can return a "not-found" value that indicates that the desired completion state will never be achieved. This return value is ignored. Sounds like a bug to me, no? Can someone please correctly handle the failure (not-found) return from libusb_cancel_transfer that's inside of sync_transfer_wait_for_completion in a manner such that the endless loop doesn't occur any more? Thanks! Dave --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/pull/167#issuecomment-66930480 |