Debugging with GDB - Jumping Go to the previous , next section. Continuing at a different address Ordinarily, when you continue your program, you do so at the place where it stopped, with the continue command.
Execution stops again immediately if there is a breakpoint there.
See section Printing source lines , for a description of the different forms of linespec . The jump command does not change the current stack frame, or the stack pointer, or the contents of any memory location or any register other than the program counter. If line linespec is in a different function from the one currently executing, the results may be bizarre if the two functions expect different patterns of arguments or of local variables. For this reason, the jump command requests confirmation if the specified line is not in the function currently executing. However, even bizarre results are predictable if you are well acquainted with the machine-language code of your program.