Properly using debugger commands in Creator

[WilliamKappler]

I'm trying to debug a case of stack corruption using Qt Creator with GDB (Windows, MSYS GCC), which requires running some custom commands, mainly,

set $pc = *(void **)$rsp
set $rsp = $rsp + 8

I've figured out how to do that via the log view and it works fine; bt prints the correct, uncorrupted stack. However... nothing in the UI updates as a result of those commands, it still shows the corrupted stack with no useful information. I would really like to be able to examine the debug state AFTER running those commands using Creator's UI.

Is there a way to "refresh" the UI to use the modified debugger state, or an alternative way to run those commands that the UI will pick up on?

(My creator install is outdated at version 4.13.2. If it makes a difference, I can upgrade it, but I generally avoid messing with what works on Windows. Very touchy development environment for open source.)