Extremely odd behaviour when debugging libusbK with CDB

Hi guys.
Looks like I've managed to stumble across some kind of reverse Heisenbug,
and it's been doing my head in for days.

I am developing a program using the Qt Library and LibusbK (precompiled
.dll/.lib).
When I compile and run, it works great - in debug or release mode.  I can
even deploy it on other machines and there are no immediate issues.
However, when I try to debug using CDB (the Qt/Visual Studio debugger),
UsbK_Init will always fail.

This is, of course, a little bit problematic.  Is there a way to get around
it?
If it helps, UsbK_Init returns error code 0x03 if compiled with Visual C++
2013 (x86 and x64), and 0xCE if compiled with MinGW x86.

Is this a known issue?  Do desktop debuggers do this often?  (If you
haven't guessed already, I have fairly minimal experience developing
Desktop software; I'm mainly used to microcontrollers and even there I'm no
expert.)

Thanks,
~Chris

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z

_______________________________________________
Libusb-win32-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel