Please add "Jump to cursor"

devs using that should be aware of possible stack issues (and GDB forbids jumping out of the function in the first place, so you have to handle the GDB error, passing it to the user), but it is very common a very useful option "please do the last 10 lines again"

Start by locating the extension's existing debugger controls and how they send commands to GDB; the issue names no files or tests. Check how GDB errors are surfaced to users. Done means users can jump execution to the cursor, and attempts GDB forbids (such as jumping out of a function) report the error without hiding it.

Written by the indexing model from the issue text.