On 2012.08.10 08:53, sebasti...@gmx-topmail.de wrote: > Some weeks ago, at the very beginning of our > investigation, I had set the LIBUSB_DEBUG variable to 3 on the production > machines, but it had no impact on the error logging.
This would indicate that the error you got on test is different from the one on prod, as I'd expect the warning to still occur (though we reorganized some of the code in the meantime, so maybe that played a bit). > BUT, on the test machine I set LIBUSB_DEBUG to 4. So, in my opinion, we > won't get more data from the production machines than the crash log on > the test machine already provides! Yeah. It all points to the same area. > I'd prefer to wait for your patch, just in case there are more changes to > the code than expected. Please consider that I'll have to replace every > change (recompiled lib) on more than 25 machines! I wasn't aware of that. I'll try to push something over the weekend then. 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
