I'll try to test this later this week, I'll get back to you.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/121#issuecomment-21708277
--
See everything from the browser to
Ok. When is 1.0.17 due?
We are using libusbx in a multi-platform application and it would be neat to be
able to use the new hotplug api in our application (without the application
crashing), with a graceful fallback, enabling us to just replace libusbx with
the new version when you support Windo
Issue at least seems to be resolved by inserting the following at line 1534:
if (itransfer->list.next)
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/121#issuecomment-21292870
---
Well, I managed to get a little more output by also changing -g to -g3 in my
app.
```
[ 6.852191] [6703] libusbx: debug [handle_events] poll() returned 1
[ 6.852199] [6703] libusbx: debug [op_handle_events] checking fd 7 with
revents = 0
nf is disconnected ? ;)
[ 6.852203] [6703] lib
Sorry, I forgot the stacktrace since it so extremely short. I tried recompiling
libusbx with
./configure CC='icc' CXX='icpc' CXXFLAGS='-O3 -g3' CCFLAGS=' -O3 -g3'
but it did not help to get anything more verbose.
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reaso
After upgrading from 1.0.15 to 1.0.16 my application crashes in libusb io.c,
line 1534
(int usbi_handle_transfer_completion(struct usbi_transfer *itransfer,
enum libusb_transfer_status status)) when unplugging a device with
active transfers. (incoming endpoints that is waiting for interru
