I am running gdb and want to examine one of those unfortunate god objects. It takes many pages (and I have a 24\" monitor turned sideways!) to see the whole thing. For eas
Extending on @qubodup's answer
gdb core.3599 -ex bt -ex quit |& tee backtrace.log
the -ex switch runs a gdb command. So the above loads the core file, runs bt command, then quit command. Output is written to backtrace.log and also on the screen.
Another useful gdb invocation (giving stacktrace with local variables from all threads) is
gdb core.3599 -ex 'thread apply all bt full' -ex quit