gdb's disas command (or asm view in general) is also very helpful, especially if you want to try control-c profiling [1] and then looking at the asm instruction

gdb's disas command (or asm view in general) is also very helpful, especially if you want to try control-c profiling [1] and then looking at the asm instructions in the neighborhood of where you halted your program. [1]: https://stackoverflow.com/questions/375913/how-can-i-profile-c-code-running-on-linux https://stackoverflow.com/questions/375913/how-can-i-profile...