Is it possible to “jump”/”skip” in GDB debugger?

by

To resume execution at a new address, use jump (short form: j):

jump LINENUM
jump *ADDRESS

The GDB manual suggests using tbreak (temporary breakpoint) before jumping.

The linenum can be any linespec expression, like +1 for the next line.

See @gospes’s answer on a related question for a handy skip macro that does exactly that.

Using jump is only “safe” in un-optimized code (-O0), and even then only within the current function. It only modifies the program counter; it doesn’t change any other registers or memory.

Only gcc -O0 compiles each source statement (or line?) into an independent block of instructions that loads variable values from memory and stores results. This lets you modify variable values with a debugger at any breakpoint, and makes jumping between lines in the machine code work like jumping between lines in the C source.

This is part of why -O0 makes such slow code: not only does the compiler not spend time optimizing, it is required to make slow code that spills/reloads everything after every statement to support asynchronous modification of variables and even program-counter. (Store/reload latency is about 5 cycles on a typical x86, so a 1 cycle add takes 6 cycles in -O0 builds).

gcc’s manual suggests using -Og for the usual edit-compile-debug cycle, but even that light level of optimization will break jump and async modification of variables. If you don’t want to do that while debugging, it’s a good choice, especially for projects where -O0 runs so slowly that it’s a problem.

To set program-counter / instruction-pointer to a new address without resuming, you can also use this:

set $pc = 0x4005a5

Copy/paste addresses from the disassembly window (layout asm / layout reg).

This is equivalent to tbreak + jump, but you can’t use line numbers, only instruction addresses. (And you don’t get a warning + confirmation-request for jumping outside the current function).

Then you can stepi from there. $pc is a generic gdb name for whatever the register is really called in the target architecture. e.g. RIP in x86-64. (See also the bottom of the x86 tag wiki for asm debugging tips for gdb.)

More Related Contents:

  1. How can I tell if a library was compiled with -g?
  2. How to print every executed line in GDB automatically until a given breakpoint is reached?
  3. Include source code of malloc.c in gdb?
  4. How to solve “ptrace operation not permitted” when trying to attach GDB to a process?
  5. Cannot insert breakpoints. Addresses with low values
  6. How do I pass a command line argument while starting up GDB in Linux? [duplicate]
  7. segfault only when NOT using debugger
  8. Debugging a linked-list
  9. Is there a good Valgrind substitute for Windows?
  10. How can one grab a stack trace in C?
  11. How to debug using gdb?
  12. How Can I debug a C program on Linux?
  13. gdb – debugging with pipe
  14. Printing all global variables/local variables?
  15. Is there a good Valgrind substitute for Windows?
  16. How to pretty-print STL containers in GDB?
  17. How to get a “codesigned” gdb on OSX?
  18. Why does gdb evaluate sqrt(3) to 0?
  19. How do I use the MinGW gdb debugger to debug a C++ program in Windows?
  20. How do I print a #defined constant in GDB?
  21. How do I debug the child process after fork() in gdb?
  22. Can’t step into string.h function with GDB
  23. gdb gives strange output when using math.h functions [duplicate]
  24. Why GDB jumps unpredictably between lines and prints variables as “”?
  25. How can a C program produce a core dump of itself without terminating?
  26. addr2line on kernel module
  27. Why does malloc allocate a different number of bytes than requested?
  28. gdb prints wrong values when modifying arguments
  29. What exactly is -fno-builtin doing here?
  30. How to avoid entering library’s source files while debugging in Qt Creator with gdb?

Leave a Comment