Describe the bug
Current release 1.12.1 advertises support for Jump to Cursor, but it appears to not be working.
To Reproduce
Steps to reproduce the behavior:
- Start debug session
- Right click line of code
- Select "Jump to Cursor"
- Error pop-up indicates "Set next statement is not supported by the current debugger"
Expected behavior
The request sets the location where the debuggee will continue to run. This makes it possible to skip the execution of code or to execute code again. The code between the current location and the goto target is not executed but skipped.
Screenshots
Environment (please complete the following information):
- Cortex-Debug Version 1.12.1
- OS: Linux Ubuntu 24.04.4 LTS
- GDB Version: 13.3.1
- Compiler Toolchain Version: arm-none-eab V 13.3.Rel1
Additional context
I found the original feature implementation for 'Jump to Cursor' in PR #417 and Issue #418, but it seems to have been broken during a refactor in commit 1ff878c.
- 6ac5c31, “Jump to cursor, PR 417”, added Jump to Cursor support
- 1ff878c, “hardwareBreakpoints to force HW only bpts”, removed the low-level MI goto helper and changed gotoTargetsRequest to create a temporary breakpoint instead
Describe the bug
Current release 1.12.1 advertises support for Jump to Cursor, but it appears to not be working.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The request sets the location where the debuggee will continue to run. This makes it possible to skip the execution of code or to execute code again. The code between the current location and the goto target is not executed but skipped.
Screenshots
Environment (please complete the following information):
Additional context
I found the original feature implementation for 'Jump to Cursor' in PR #417 and Issue #418, but it seems to have been broken during a refactor in commit 1ff878c.