Detailed description
In this PR we address the issue of BMDA not always picking up the registry path to the serial interfaces due to the instance ID coming back as an empty string. It turns out that this is because of the behaviour of assertions under certain versions of the assert.h header when in release mode builds.
This fixes the ability for BMDA to find probes under Windows 11.
Your checklist for this pull request
- I've read the Code of Conduct
- I've read the guidelines for contributing to this repository
- It builds for hardware native (see Building the firmware)
- It builds as BMDA (see Building the BMDA)
- I've tested it to the best of my ability
- My commit messages provide a useful short description of what the commits do
Closing issues
Fixes #2174
<!-- Filling this template is mandatory -->
## Detailed description
In this PR we address the issue of BMDA not always picking up the registry path to the serial interfaces due to the instance ID coming back as an empty string. It turns out that this is because of the behaviour of assertions under certain versions of the assert.h header when in release mode builds.
This fixes the ability for BMDA to find probes under Windows 11.
## Your checklist for this pull request
* [x] I've read the [Code of Conduct](https://codeberg.org/blackmagic-debug/blackmagic/src/CODE_OF_CONDUCT.md)
* [x] I've read the [guidelines for contributing](https://codeberg.org/blackmagic-debug/blackmagic/src/CONTRIBUTING.md) to this repository
* [x] It builds for hardware native (see [Building the firmware](https://codeberg.org/blackmagic-debug/blackmagic?tab=readme-ov-file#building-the-firmware))
* [x] It builds as BMDA (see [Building the BMDA](https://codeberg.org/blackmagic-debug/blackmagic?tab=readme-ov-file#building-black-magic-debug-app))
* [x] I've tested it to the best of my ability
* [x] My commit messages provide a useful short description of what the commits do
## Closing issues
Fixes #2174