Comments on: GDB Annoyances: Incomplete Stack Trace https://www.dumpanalysis.org/blog/index.php/2012/03/25/gdb-annoyances-incomplete-stack-trace/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Wed, 06 May 2026 15:11:42 +0000 http://wordpress.org/?v=2.3.3 By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2012/03/25/gdb-annoyances-incomplete-stack-trace/#comment-741691 Dmitry Vostokov Fri, 18 Dec 2015 20:43:34 +0000 https://www.dumpanalysis.org/blog/index.php/2012/03/25/gdb-annoyances-incomplete-stack-trace/#comment-741691 For Linux we have: (gdb) set backtrace past-main (gdb) bt #0 0x000000000042fed1 in nanosleep () #1 0x000000000042fda0 in sleep () #2 0x000000000040078a in main () #3 0x0000000000405283 in __libc_start_main () #4 0x00000000004003e9 in _start () For Linux we have:

(gdb) set backtrace past-main

(gdb) bt
#0 0×000000000042fed1 in nanosleep ()
#1 0×000000000042fda0 in sleep ()
#2 0×000000000040078a in main ()
#3 0×0000000000405283 in __libc_start_main ()
#4 0×00000000004003e9 in _start ()

]]>