You can set new breakpoints in gdb while you are debugging as described here. E.g. break filename:linenumber will add a new breakpoint which will be hit if you continue the execution in gdb.
Sorry for my slow response; and probably for the very basic question; but to double check I’m not missing something. The below console output shows the error I get trying to set a “break” after run.
I think the >>> indicates I’m inputting to a python interpreter; so makes sense the gdb commands aren’t going to have an affect there. But if I ctr-c out of the running program; I have to re-import; which is just a bit slow