On 2012.08.15 23:18, Pete Batard wrote: > By the looks of it, the error you got on the test environment isn't the > same as the one you get in prod, though I still wouldn't mind figuring > out the cause of what happened in test. The test machine is still running with LIBUSB_DEBUG set to 4. Do you know how you will do that? It is unlikely that the error will occur again so quickly...
> 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. > PS: Can I ask you to reply to posts from the thread if possible? At > least Thunderbird doesn't seem to pick up the previous messages when > using thread view, which makes me think you're not replying to existing > posts or something. This results in new messages on this issue appearing > in their own new thread and makes it more troublesome to reference > previous data. No big deal - just makes life a bit easier to keep all > data pertaining to the same issue in the same thread. Sorry for that! I'll use Thunderbird for further posts to the list. ========= Regards Sebastian ========= ------------------------------------------------------------------------------ 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
