Restart not updating code location in editor about cortex-debug HOT 17 CLOSED

Thanks for the report - I had this problem before and I thought I was completely fixed, but perhaps it is still happening in some cases.

What is your OS and VS Code versions? Also, what GDB server are you using?

from cortex-debug.

OS Ubuntu Gnome 16.04, VS Code 1.22.2, Cortex Debug plugin, says 0.1.19 in the extensions left hand pane, but the changelog only goes to 0.1.18.

GDB server is JLinkGDBServer 6.22g (I did update to 6.32, but downgraded after I had some problems that in hindsight were probably related to Eclipse).

from cortex-debug.

Thanks for the details; will try to have a look soon.

from cortex-debug.

Also the runToMain option works well after starting the debug session, but when pressing restart, then step, I am stepped into the init functions, not main.

from cortex-debug.

Yes, at the moment the runToMain functionality hasn't been implemented in the restart request. The reason for that is with many core/debugger combinations have a very limited number of breakpoints they can use (often as little as 2) - so when restarting I can't guarantee that I can actually set the temporary breakpoint. I need to add some functionality so that it can remove the breakpoints for the runToMain step and then re-create them after it breaks at main; until I have a chance to do that I can't implement the runToMain in a reliable fashion in the restart situation.

from cortex-debug.

I found that appending a command 'target-download' can make it jump to the init function correctly when click on restart.
like this:

from cortex-debug.

Can you provide more details about your restartCommands? any chance you would be willing to show which file it goes into? Thanks.

from cortex-debug.

@Marus Can you test if it is working using my solution see above. It works fine on my side.

from cortex-debug.

from cortex-debug.

It is better if you can find the root cause. This is only a workaround for me to use.

from cortex-debug.

@Marus Have a plan to fix this?

from cortex-debug.

Is there a fix for this issue in the making?

from cortex-debug.

Btw, if you are using an RTOS, this is a common problem with OpenOCD and JLink especially if you have runToMain disabled. GDB never gets an updated stack

from cortex-debug.

Alright. Though I am not using a RTOS nor JLink. I have the Tiva Launchpad tm4c123gxl and connect with Stellaris ICDI JTAG/SWD interface.

from cortex-debug.

@rk-exxec Sorry to hear that. Does a single step fix the issue? We only report what GDB reports

from cortex-debug.

yes, when I step then the position is shown correctly again.

from cortex-debug.

There is no workaround for this. Not with gdb and most of the gdb-servers. With OpenOCD, there is a workaround that is used in VSCode (changes in master, not yet released).

Note that this only happens if you enable breakAfterReset which is no longer the default, so you don't see this problem anymore.

The final workaround (for servers other than OpenOCD) is to do a single step to get the real stack trace. I have not found any gdb-trick to fix this. So, I am closing this issue

from cortex-debug.