On Sun, Jun 17, 2012 at 10:33 PM, Ellis Whitehead <ellis.whiteh...@gmail.com> wrote: >>> You can produce detailed debug log if you set the environmental >>> variable LIBUSB_DEBUG to 4. That debug log may help to identify >>> the potential problem. > > Ok, I've uploaded it here: > http://gcead.sourceforge.net/libusbx-debug-20120617.log > I issued the command to start recording at timestamp [12.054910]. Due > to the large number of debug lines, I stopped recording at > [12.528804]. Shutdown was at [18.014753]. >
Indeed this looks like a potential problem in the Mac OS X backend. What is the Mac OS X version you are using? Could you post the details about your device (eg: USB Prober output about your device, or "lsusb -vvv" under Linux or the USBView output under Windows)? I do not know much about the details of the OS X backend but hopefully others can help you here. -- Xiaofan ------------------------------------------------------------------------------ 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
