Hi all, I read already some threads here in the list about the "hot disconnect" and the issues that happen.
I'm using the libusbx 1.0.17 and encounter the following stacktrace when removing a usb device during a transfer - the timeout is set to 50 (msec) /lib/libusb-1.0.so.0 [0xb7037f94] /lib/libusb-1.0.so.0 [0xb7037ea2] /lib/libusb-1.0.so.0:libusb_handle_events_completed() /lib/libusb-1.0.so.0:libusb_handle_events_timeout_completed() /lib/libusb-1.0.so.0 [0xb7036caa] /lib/libusb-1.0.so.0 [0xb703b27a] /lib/libc.so.6:ioctl() this stays for several seconds until I send a SEGV to the process: /lib/libusb-1.0.so.0 [0xb7037f94] /lib/libusb-1.0.so.0 [0xb7037ea2] /lib/libusb-1.0.so.0:libusb_handle_events_completed() /lib/libusb-1.0.so.0:libusb_handle_events_timeout_completed() /lib/libusb-1.0.so.0 [0xb7036caa] /lib/libusb-1.0.so.0 [0xb703b27a] /lib/libusb-1.0.so.0 [0xb7038ab6] /lib/libusb-1.0.so.0 [0xb7031fe0] /lib/libusb-1.0.so.0 [0xb7031c9c] That's it. Additonally I had a SEGV also when removing the USB device, but I wasn't able to catch the stack there, sorry. I know that the handling of the real disconnect may have several failing transfers before the disconnect is actually reported. But are there possibilities to prevent the process to stall or to SEGV? Maybe there is an easy workaround for that? Thanks. Best regards, Erik ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
