On 16 August 2012 12:46, sebastiank <sebasti...@gmx-topmail.de> wrote: > The test machine is still running with LIBUSB_DEBUG set to 4. Do you > know how you will do that?
If you're using the version of libusbx with the latest patches, we will get the needed inisght about the cause for the error. > It is unlikely that the error will occur again so quickly... Not a problem. Even if it takes a year for the error to reoccur, we'll want to hear about the new details you get in the log then. >> So far, the only potential issue I see that may alleviate your problem >> is the "if (r && (r != LIBUSB_ERROR_BUSY))" change I mentioned on >> 2012.08.03, so I may push a patch with that to see how it goes. > Don't know if I understand it right, but the libusbx on the test and > prod were already compiled this line of code. It was included, when > the segmentation fault on the test happened. OK. I didn't think you had applied it. In that case, I don't really have any potential fix to push, and trying to add instrumentation may be tricky. Will see what I can do. Regards, /Pete ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
