Hi, I'm in the middle of tracking down (and hopefully fixing) a rare memory fault in the desktop Windows version of libusbx*.
When the issue was reported by one of our internal testers it wasn't possible for me to decode the Windows Error Reporting (WER) information in any sensible way as I didn't have the .pdb files for libusbx. Would it make sense to create a zip of the symbols for the pre-compiled binaries available on sourceforge? I don't remember any users ever providing Window error report information (such as minidumps ) so I'm not sure that it would be worth the extra effort for the maintainer producing the pre-built binaries (i.e. Pete). Regards, Toby * - it seems to be caused by having one thread inside handle events while another thread is attempting to submit a transfer. The thread which is handling events attempts to dereference a null pointer when checking HasOverlappedIoCompletedSync inside windows_handle_events. ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
