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

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.

Reproduce the issue by debugging a function and entering the gdb `up` command, then trace the code-browser update path in the TypeScript/React frontend. Done means the browser view changes to the upper stack frame after the command; the payload names no specific file or test to begin with.

Written by the indexing model from the issue text.