ThreadDebug Lib - Unresponsive After Start

Hello All,

Originally discussed here: [https://github.com/arduino/ArduinoCore-mbed/issues/16](url)

I've tried using the ThreadDebug Library with the Portanta_M7 - at the top of my sketch:

#include

// UartDebugCommInterface debugComm(SERIAL1_TX, SERIAL1_RX, 230400);
// ThreadDebug threadDebug(&debugComm, DEBUG_BREAK_IN_SETUP);

UsbDebugCommInterface debugComm(&SerialUSB);
ThreadDebug threadDebug(&debugComm, DEBUG_BREAK_IN_SETUP);

---
The debug console window prints:
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from c:/temp/Display/Display.arduinobeta.mbed.envie_m7.elf...
done.
GDB unhandled notify: cmd-param-changed: {"param":"pagination","value":"off"}
GDB unhandled notify: cmd-param-changed: {"param":"target-charset","value":"ASCII"}
Remote debugging using COM4

If I type show configuration it says:
Please start a debug session to evaluate - but a debug session is running.

---

Another session where it just disconnects after starting:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from c:/temp/Display/Display.arduinobeta.mbed.envie_m7.elf...
done.
GDB unhandled notify: cmd-param-changed: {"param":"pagination","value":"off"}
GDB unhandled notify: cmd-param-changed: {"param":"target-charset","value":"ASCII"}
Remote debugging using COM4
setup () at c:\temp\Display/Display.ino:214
214 {
Will reset on next continue.
Note: automatically using hardware breakpoints for read-only addresses.
Remote connection closed
---

So, any help appreciated.

Thanks,
John W.

Start by reviewing the ThreadDebug setup in the Display.ino sketch around line 214 and reproduce both debug-console outcomes over COM4. Compare the session that remains unresponsive with the one that reports “Remote connection closed”; the issue is done when the cause is identified and the debug session reliably starts or the required limitation is documented.

Written by the indexing model from the issue text.