Those bogus adresses (0x00000002 and the like) are actually PC values, not SP values. Now, when you get this kind of SEGV, with a bogus (very small) PC address, 99% of the time it’s due to calling through a bogus function pointer. Note that virtual calls in C++ are implemented via function pointers, so any … Read more
This error occurs because OSX implements a pid access policy which requires a digital signature for binaries to access other processes pids. To enable gdb access to other processes, we must first code sign the binary. This signature depends on a particular certificate, which the user must create and register with the system. To create … Read more
You need to enable logging: (gdb) set logging on Now GDB will log to ./gdb.txt. You can tell it which file to use: (gdb) set logging file my_god_object.log And you can examine the current logging configuration: (gdb) show logging
info frame to show the stack frame info To read the memory at given addresses you should take a look at x x/x $esp for hex x/d $esp for signed x/u $esp for unsigned etc. x uses the format syntax, you could also take a look at the current instruction via x/i $eip etc.
backtrace full: Complete backtrace with local variables up, down, frame: Move through frames watch: Suspend the process when a certain condition is met set print pretty on: Prints out prettily formatted C source code set logging on: Log debugging session to show to others for support set print array on: Pretty array printing finish: Continue … Read more
One way is to signal an interrupt: #include <csignal> // Generate an interrupt std::raise(SIGINT); In C: #include <signal.h> raise(SIGINT); UPDATE: Microsoft Docs says that Windows doesn’t really support SIGINT, so if portability is a concern, you’re probably better off using SIGABRT. SIGINT is not supported for any Win32 application. When a CTRL+C interrupt occurs, Win32 … Read more
You can attach to a running process with gdb -p PID.
It’s called the TUI (no kidding). Start for example with gdbtui or gdb -tui … Please also see this answer by Ciro Santilli. It wasn’t available in 2012 to the best of my knowledge, but definitely worth a look.
From the docs: -g Produce debugging information in the operating system’s native format (stabs, COFF, XCOFF, or DWARF 2). GDB can work with this debugging information. On most systems that use stabs format, -g enables use of extra debugging information that only GDB can use; this extra information makes debugging work better in GDB but … Read more
As of GDB 7.2 (2011-08-23) you can now use the save breakpoints command. save breakpoints <filename> Save all current breakpoint definitions to a file suitable for use in a later debugging session. To read the saved breakpoint definitions, use the `source’ command. Use source <filename> to restore the saved breakpoints from the file.