Fix for 'libusb_devices were leaked' when no ST-LINK programmer was found #1150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When searching for interfaces, the libstlink is not unreferencing the probed USB devices when no ST-LINK programmer was found, leading to "libsub_devices were leaked" warnings, as shown below:
This warning is evidenced when using the libstlink to poll for ST-LINK interfaces on Windows (I am developing an application that waits for a ST-LINK programmer to be connected.)
A description of the problem and solution can be found here:
https://libusb-devel.narkive.com/KfZ3490q/warning-some-libusb-devices-were-leaked