Well, this wasn’t easy – but I think I somewhat got it 🙂 I went through a bunch of failed attempts (posted here); relevant code is below. Basically, the problem in a “next/step until breakpoint” is how to determine whether you’re “on” a breakpoint or not, if the debugger is stopped (at a step). Note … Read more
import gdb only works when your Python code is running within the GDB process. It’s not supposed to work from the regular system Python interpreter. Explanation GDB embeds the Python interpreter so it can use Python as an extension language. You can’t just import gdb from /usr/bin/python like it’s an ordinary Python library because GDB … Read more
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.
KDbg (http://www.kdbg.org/)
The other possibility i can think of is: 1.Your process is running more than one thread. For eg – 2 say x & y. 2.Thread y hits the break point but you have attached gdb to thread x. This case is a Trace/breakpoint trap.
If you use GDB 7.4 together with Valgrind 3.7.0, then you have unlimited “emulated” hardware watchpoints. Start your program under Valgrind, giving the arguments –vgdb=full –vgdb-error=0 then use GDB to connect to it (target remote | vgdb). Then you can e.g. watch or awatch or rwatch a memory range by doing rwatch (char[100]) *0x5180040 See … Read more
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
download the most recent GDB from https://www.sourceware.org/gdb/download/ expand the gdb-7.12.1.tar.xz file: tar xopf gdb-7.12.1.tar.xz cd gdb-7.12.1 in terminal to open the gdb folder then follow the instructions in the README file in the gdb folder, or simply follow the following steps: ./configure, wait for the terminal make and wait again (which can take some time) … Read more
To do this, you need to activate the instruction-recording target, by executing the command record from the point where you want to go forward and backward (remember that the recording will significantly slow down the execution, especially if you have several threads!) I’ve just checked that it’s working correctly: (gdb) info threads Id Target Id … Read more