Stepping through code kills the debug session about cortex-debug HOT 3 CLOSED

Same here, removing the RTOS option from config makes a huge difference. No GDB weirdness since... fingers crossed for me...

from cortex-debug.

"rtos": "FreeRTOS",

We don't do anything with the RTOS. We simply pass it to JLink. You can see that in the Debug Console. All your RTOS magic is between GDB and JLinkGDBServerCLExe. We have nothing to do with it.

For JLink, you have to actually pass the path to the DLL/so. I think the path can be relative to JLink install dir. We attempt to convert a simple name to the name of a DLL/so but best way is for you to supply that yourself.

You did not attach the contents of the Terminal where JLinkServer output exists. JLink may have crashed. You can probably see what is going on over there. YOu also did not provide the contents of Debug Console.

Please contact SEGGER if you are having issues if the JLink command line looks okay

from cortex-debug.

I am closing this as it is not a problem with this extension. Since no relevant information from the Debug Console or from the TERMINAL(gdb-server) is provided, nothing here is actionable.

Please use triple back-quotes for things that look like code/XML/JSON or things that are not a conversation (logs, output, etc.). It is part of markdown.

from cortex-debug.