You should have a copy of arm-eabi-addr2line available in the NDK bin directory. You can use this with a command like: arm-eabi-addr2line -f -e /path/to/lib/with/symbols.so 0x001fb18a That will crawl through the debug symbols in the shared lib to get file and line number information. For best results hand it a library that hasn’t had the … Read more
This is easy, actually. I’ll give you the bare bones, and you can modify to suit. (gdb) define nstep > set $foo = $arg0 > while ($foo–) > step > end > end (gdb) nstep 100 I’ve done this many times. Hope this helps!
You could enable floating point exceptions – see glibc Control Functions – then you’ll get a SIGFPE when your NaN value is produced
The first step is to compile your program with -g to include debugging information within the executable: g++ -g -o myprog.exe mycode.cpp Then the program can be loaded into gdb: gdb myprog.exe A few commands to get you started: break main will cause the debugger to break when main is called. You can also break … Read more
I.1 Codesigning the Debugger The Darwin Kernel requires the debugger to have special permissions before it is allowed to control other processes. These permissions are granted by codesigning the GDB executable. Without these permissions, the debugger will report error messages such as: Starting program: /x/y/foo Unable to find Mach task port for process-id 28885: (os/kern) … Read more
In GDB 7.2: (gdb) help info proc Show /proc process information about any running process. Specify any process id, or use the program being debugged by default. Specify any of the following keywords for detailed info: mappings — list of mapped memory regions. stat — list a bunch of random process info. status — list … Read more
Replying to myself, I’d like to give the answer that someone gave me on IRC: (gdb) apropos pending actions — Specify the actions to be taken at a tracepoint set breakpoint — Breakpoint specific settings set breakpoint pending — Set debugger’s behavior regarding pending breakpoints show breakpoint — Breakpoint specific settings show breakpoint pending — … Read more
The easiest is setting a program variable (see GDB: assignment): (gdb) l 6 { 7 int i; 8 struct file *f, *ftmp; 9 (gdb) set variable i = 10 (gdb) p i $1 = 10 Or you can just update arbitrary (writable) location by address: (gdb) set {int}0x83040 = 4 There’s more. Read the manual.
You need to enable logging: (gdb) set logging on Now GDB will log to ./gdb.txt. You can tell it which file to use: (gdb) set logging file my_god_object.log And you can examine the current logging configuration: (gdb) show logging
Once gdb starts, you can run the program using “r args“. So if you are running your code by: $ executablefile arg1 arg2 arg3 Debug it on gdb by: $ gdb executablefile (gdb) r arg1 arg2 arg3