OK, a few things: 1. Testing with the latest git version would be nice. We added some modifications for timeout handling, and it's always good not to try to figure out that an issue is one that has already been addressed. I don't exactly expect yours to have been, but I wouldn't mind being sure. 2. A libusbx debug log is even nicer. A stack trace doesn't provide much information about what was happening before the crash. Just make sure you issue: "set LIBUSB_DEBUG=4" on the commandline before running your console application 3. If you're recompiling libusbx, please uncomment the following in poll_windows.c: "//#define DEBUG_POLL_WINDOWS" (line 51). It should also help with troubleshooting 4. Since you'll be using the git version, try your test application with the libusbK or libusb0 drivers, that are now supported, to find out if it crashes in the same fashion 5. You may also want to add a debug printout of winusb_handle and transfer->endpoint before the WinUsb_AbortPipe() line (using usbi_dbg).
Regards, /Pete ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
