The gdb up command does not move to the previous frame in the code browser

[vineethkartha]

During debugging a function if I give the 'up' command in gdb, the code shown in the browser does not update to the upper frame.

[cs01]

Thanks for filing this. I think you're right. The variables update but the selected frame doesn't. I'll look into it when I get a chance.

Another way to get the source code shown for the parent frame is to click the name of the function in the "Threads" section in the top right. This will switch the frame and display the variables of the calling frame.

You can also just click the source file name in that same table to view the source without switching frame context.

[GitMensch]

The up command and others send mi events that should be catched. Doing so has the benefit that it also works when a script or python executes such commands.

Vim's TermDebug uses '^(*stopped|*running|=thread-selected)'.