The first step is to compile your program with -g to include debugging information within the executable: g++ -g -o myprog.exe mycode.cpp Then the program can be loaded into gdb: gdb myprog.exe A few commands to get you started: break main will cause the debugger to break when main is called. You can also break … Read more
set output-radix 16 (and set output-radix 10 to switch it back).
Start gdb without specifying the executable or core file, then type the following commands: set solib-absolute-prefix ./usr file path/to/executable core-file path/to/corefile You will need to make sure to mirror your library path exactly from the target system. The above is meant for debugging targets that don’t match your host, that is why it’s important to … Read more
A more compact solution: p /a (*(void ***)obj)[0]@10
Had the exact same problem. Have you tried GDB user-defined hooks or commands ? In your ~/.gdbinit or in your session, you can do: define hook-next refresh end This will call the refresh command each time you enter the next command or one of its aliases. Or you can define: define mynext next refresh end … Read more
“Inferior” is a general term to mean “something that you are using gdb to debug” — generally a process or perhaps a kernel running on an emulator or on some other piece of hardware connected on a serial line. The term “Inferior debugger” comes up when you are using gdb to debug gdb. That is, … Read more
(gdb) set breakpoint pending on This will make gdb skip asking for confirmation, quote from the docs: This indicates that an unrecognized breakpoint location should automatically result in a pending breakpoint being created.
Earlier answers were correct when written (in 2013), but since then gdb and libstdc++ have changed. libstdc++ now has some hooks that let gdb interact more nicely with the exception system. In particular, there is now enough information exposed for gdb to provide a $_exception convenience variable to the user. This variable holds the exception … Read more
gdb is not supported on M1 Macs; you can instead consider using lldb.
In addition to options mentioned by @diverscuba23, you could do the following: gdb –args bash <script> (assuming it’s a bash script. Else adapt accordingly)