Haneef Mohammed

We are expecting instructions in sorted order as well. Can you do the following? * Set "showDevDebugOutput": "none" in launch.json * Run until you get to your breakpoint * In...

I used the start and end addresses by looking at what was in the Debug Console at the time. If your program has changed, please adjust the `disassemble` command accordingly.

Good detective work! It is still possible that we are doing something wrong. Let us verify that we are sending VSCode a proper response. VSCode is not supposed to interpret...

> I'm using GCC for ARM. Why would you think otherwise? Because I saw the `.axf` extension. Typically used by uVision I think (or IAR). Sure you can use any...

Heheh. Yes, building VSCode is a challenge, but hopefully we don't need that. Lines starting with `From client:` are requests from VSCode. Lines starting with `To client:` are a response...

Aaaarghhh. I would like to not go into the VSCode code base. In this case, I know who authored it, he may accept a PR. But, it is still hard...

We do not manage ANY of the editor windows in VSCode -- not your source code or the disassembly view. It is done by VSCode proper. Please submit an issue...

I think I understand what is going on. OpenOCD (any gdb-server) gets one chance to query gdb for symbol info and that is at the very start of the session....

Good to know. *If/When* this gets fixed, I will need help testing it. I will report back here. This will be a large enough (dangerous) change that it may require...

``` Target unknown error 32 Error in initializing ST-LINK device. Reason: Unknown. Please check power and cabling to target. ``` Well, you are getting this error from ST-LINK on startup....