On 2012.06.12 22:18, Markus wrote:
> I don't see any debug messages (though I enabled the libusbx debug
> facility in my code, level 3).

Try level 4. 4 is the level to set for debug, not 3.

If you're using a version earlier than 1.0.11.10519, you will also have 
to compile with either --enable-debug-log if using MinGW/cygwin, or turn 
the debug logging option on in msvc/config.h.

But if you're using an older version, I would advise you to upgrade 
first (we have an 1.0.12-rc1 available, along with Windows binaries 
which I just uploaded) as it makes it a lot easier to obtain debug info 
there: If your program is a console application, you can just set the 
environmental variable LIBUSB_DEBUG to 4. Or you can just use 
libusb_set_debug(NULL, LOG_LEVEL_DEBUG) at any time during your program.

> Would I see the WinUSB error code in the libusbx debug log?

You should at least get an extra message indicating the stall detection.

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

Reply via email to