Two options: up 200 will bring you up 200 frames If you know the initial caller of the recursive routine, you can do f[rame] <caller-func> – this will jump to the frame of address caller-func. See Frame Selection in the manual.
(gdb) help shell Execute the rest of the line as a shell command. With no arguments, run an inferior shell. After finish, you can use ‘exit’ to return to gdb.
write the commands in a file and execute gdb with -x switch gdb -x command_file_name or run the gdb source command while gdb is running if you dont want to specify a command file from command line >source [-s] [-v] command_file_name
You can use: info registers eflags to get the entire set of flags. You’ll see a line like: eflags 0x41 [ CF ZF ] which means that the eflags register is set to 0x41, with the carry and zero flags set.
Yes, here is how to make this work: // sample.h struct sample { int i; struct sample *less; struct sample *more; }; // main.c #include <stdio.h> #include <assert.h> #include “sample.h” int main() { struct sample sm; sm.i = 42; sm.less = sm.more = &sm; printf(“&sm = %p\n”, &sm); assert(sm.i == 0); // will fail } … Read more
From man gdb(1): -x file Execute GDB commands from file file. You could then put your breakpoints in a file: break [file:]function break [file:]function …
As TazMainiac said, scheduler-locking is useful for single stepping, but the “mode” must be set to “step”. set scheduler-locking step You can refer the link provided by TazMainiac which mentions the same: http://ftp.gnu.org/old-gnu/Manuals/gdb-5.1.1/html_node/gdb_39.html The step mode optimizes for single-stepping. It stops other threads from “seizing the prompt” by preempting the current thread while you are … Read more
Check out the GDB Internals Manual, which covers some of the important aspects. There’s also an older PDF version of this document. From the manual: This document documents the internals of the GNU debugger, gdb. It includes description of gdb’s key algorithms and operations, as well as the mechanisms that adapt gdb to specific hosts … Read more
I agree with Dave that a conditional breakpoint is the way to go. However, to do what you asked, you can use GDB’s commands command to set a list of GDB commands to execute whenever a breakpoint is hit. I find this incredibly useful. I suggest writing your GDB commands into a file so that … Read more
Here is my script called gdbwait: #!/bin/sh progstr=$1 progpid=`pgrep -o $progstr` while [ “$progpid” = “” ]; do progpid=`pgrep -o $progstr` done gdb -ex continue -p $progpid Usage: gdbwait my_program Sure it can be written nicer but Bourne shell script syntax is painful for me so if it works then I leave it alone. 🙂 … Read more