On Wed, Jan 30, 2013 at 1:12 AM, Mohamed HAMZAOUI <requin...@gmail.com> wrote: > Another remark : I found the same problem in an old libusb ticket > http://www.libusb.org/ticket/140 > maybe the memory corruption is caused by pthread-win32 in a stress context ?
Just for reference here. Please take note the following may not have anything to do with the issues you have. This libusb.org Ticket 140 is also replicated in libusbx github issue list. https://github.com/libusbx/libusbx/issues/52 Initially the though is that it has something to do with the lack of CancelIoEx(). Ref: http://libusb.6.n5.nabble.com/poll-windows-c-Unable-to-cancel-I-O-that-was-started-from-another-thread-td4850087.html But then the same issue happened in Windows 7 as well where CancelIoEx() does exist and libusbx will use it. So the issue is not related to CancelIoEx() after all. Ref: http://libusb.6.n5.nabble.com/Strange-issues-with-libusb-and-libusb-x-td5710663.html#a5710667 -- Xiaofan ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
