BMDA - Unable to use ctrl+c to kill the task, local echo disabled disabled after killing from task manager.

[hydra]

I'm unable to use Ctrl+C to kill BMDA (blackmagic.exe) when it's running, it has to be killed by the Windows task manager. However after the process is killed local echo is disabled.

Local echo can be restored using either stty echo or reset.

BMDA was built using Cygwin, on Windows 10 x86_64.

make -j 30 clean && make -j 30 PROBE_HOST=hosted HOSTED_BMP_ONLY=0 ENABLE_RTT=1 ENABLE_DEBUG=1

Binaries attached: bmda.zip

The actual source-code used for this build is as follows:

3b48b05c (HEAD -> feature/stm32h5-stm32h7-support) target/imxrt: Fix probes' debug build by guarding hosted-only prints
3b36c340 Merge remote-tracking branch 'origin/fix/adiv5-ap-correctness' into feature/stm32h5-stm32h7-support
82702055 (origin/fix/adiv5-ap-correctness) adiv5: Improved the ROM and component outputs in adiv5_component_probe()
728444a1 adiv5_swdp: Cleaned up the DPIDR reads during multidrop scan to reduce the noise created when they fail
af71c227 adiv5: Unified the formatting of AP numbers in adiv5_new_ap()
c4a3e5c4 adiv5: Fixed the AP type display in adiv5_new_ap()
b850979e adiv5: Defined translations of all the known ARM AP types
0205d010 adiv5: Cleaned up the existing use of the IDR register in adiv5_new_ap()
d49586af adiv5: Defined macros for the various IDR register fields
d9fc6ce5 common/stm32/serialno: Fixed a mis-capitalisation of `#warning` in read_serial_number()
13cb7536 adiv5: Implemented proper handling for TrustZone in the CSW initial calculation
e3d62e3a misc: Update the clang-tidy rules to not lint on variables with 2 letter names, so 'ap' and 'dp' are considered OK
1d2e6f6d (origin/feature/stm32h5-stm32h7-support) stm32h5: Switched target identification to using the AP part number
...

However this has been happening for a while and is probably unrelated to the branches I was testing today.

[dragonmux]

👋🏼 just got to looking at this bug finally and it looks like we inadvertently fixed it when fixing a different bug. Please can you give the latest main a test and let us know if the bug persists for you or not. We'll mark this as v2.0 milestone and move accordingly.

[dragonmux]

As we've not heard back from this and we could not reproduce the issue ourself any more, we are going to close this as fixed. If it is not, please open a new issue or re-open this one and let us know.