How to set a breakpoint in GDB where the function returns?

by

Contrary to answers so far, most compilers will create a single return assembly instruction, regardless of how many return statements are in the function (it is convenient for the compiler to do that, so there is only a single place to perform all the stack frame cleanup).

If you wanted to stop on that instruction, all you have to do is disas and look for retq (or whatever the return instruction for your processor is), and set a breakpoint on it. For example:

int foo(int x)
{
  switch(x) {
   case 1: return 2;
   case 2: return 3;
   default: return 42;
  }
}

int main()
{
  return foo(0);
}


(gdb) disas foo
Dump of assembler code for function foo:
   0x0000000000400448 <+0>: push   %rbp
   0x0000000000400449 <+1>: mov    %rsp,%rbp
   0x000000000040044c <+4>: mov    %edi,-0x4(%rbp)
   0x000000000040044f <+7>: mov    -0x4(%rbp),%eax
   0x0000000000400452 <+10>:    mov    %eax,-0xc(%rbp)
   0x0000000000400455 <+13>:    cmpl   $0x1,-0xc(%rbp)
   0x0000000000400459 <+17>:    je     0x400463 <foo+27>
   0x000000000040045b <+19>:    cmpl   $0x2,-0xc(%rbp)
   0x000000000040045f <+23>:    je     0x40046c <foo+36>
   0x0000000000400461 <+25>:    jmp    0x400475 <foo+45>
   0x0000000000400463 <+27>:    movl   $0x2,-0x8(%rbp)
   0x000000000040046a <+34>:    jmp    0x40047c <foo+52>
   0x000000000040046c <+36>:    movl   $0x3,-0x8(%rbp)
   0x0000000000400473 <+43>:    jmp    0x40047c <foo+52>
   0x0000000000400475 <+45>:    movl   $0x2a,-0x8(%rbp)
   0x000000000040047c <+52>:    mov    -0x8(%rbp),%eax
   0x000000000040047f <+55>:    leaveq 
   0x0000000000400480 <+56>:    retq   
End of assembler dump.
(gdb) b *0x0000000000400480
Breakpoint 1 at 0x400480
(gdb) r

Breakpoint 1, 0x0000000000400480 in foo ()
(gdb) p $rax
$1 = 42

More Related Contents:

  1. Can I set a breakpoint on ‘memory access’ in GDB?
  2. Debugging core files generated on a Customer’s box
  3. How do I print the elements of a C++ vector in GDB?
  4. Run an Application in GDB Until an Exception Occurs
  5. How do I print the full value of a long string in gdb?
  6. How to pretty-print STL containers in GDB?
  7. How to get a “codesigned” gdb on OSX?
  8. How do I use the MinGW gdb debugger to debug a C++ program in Windows?
  9. How to pass arguments and redirect stdin from a file to program run in gdb?
  10. How to avoid entering library’s source files while debugging in Qt Creator with gdb?
  11. Debugging with command-line parameters in Visual Studio
  12. _DEBUG vs NDEBUG
  13. How to debug heap corruption errors?
  14. __FILE__, __LINE__, and __FUNCTION__ usage in C++
  15. View array in Visual Studio debugger? [duplicate]
  16. Program only crashes as release build — how to debug?
  17. Is it possible to “jump”/”skip” in GDB debugger?
  18. Tell gdb to skip standard files
  19. Why is std::cout not printing the correct value for my int8_t number?
  20. How to solve “ptrace operation not permitted” when trying to attach GDB to a process?
  21. error LNK2038: mismatch detected for ‘_ITERATOR_DEBUG_LEVEL’: value ‘0’ doesn’t match value ‘2’ in main.obj
  22. Can the “Application Error” dialog box be disabled?
  23. Cannot insert breakpoints. Addresses with low values
  24. How to set breakpoints on future shared libraries with a command flag
  25. “Cannot evaluate function — may be in-lined” error in GDB for STL template container
  26. Why do I get _CrtIsValidHeapPointer(block) and/or is_block_type_valid(header->_block_use) assertions?
  27. How do I pass a command line argument while starting up GDB in Linux? [duplicate]
  28. What are data breakpoints?
  29. traceback a pointer in c++ code gdb
  30. What does static_assert do, and what would you use it for?

Leave a Comment