I would chalk this up to differences between OS versions, configurations, devices, etc and move on. I see all memory is released. At least it does not crash and burn badly.
The function call you want to play with is: libusb_set_debug http://libusb.sourceforge.net/api-1.0/group__lib.html#ga5f8376b7a863a5a8d5b8824feb8a427a Of course, you can set the level dynamically, from your program. On Thu, Aug 29, 2019 at 12:34 PM James Richters < ja...@productionautomation.net> wrote: > At least I can shut off the messages with that.. but any idea what these > messages actually mean? It’s an init_device error but no one was tying to > do anything but get the list of devices from the system. > > > > Is there a description of the verbosity level anywhere? > > > > Is this a variable I can change during program execution without > re-compiling it? It would be helpful if I was having an issue to turn on > debug info, then turn it back off without exiting my program or needing to > compile. > > > > James > > > > > > >libusb has a debug verbosity level which currently is set to 3 (i.e., > very verbose) in the device open function. > > >There is a define in libusbx.pas that you can change to shut off debug > messages. > _______________________________________________ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal >
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
