Here is a quick start tutorial for gdb: /* test.c */ /* Sample program to debug. */ #include <stdio.h> #include <stdlib.h> int main (int argc, char **argv) { if (argc != 3) return 1; int a = atoi (argv[1]); int b = atoi (argv[2]); int c = a + b; printf (“%d\n”, c); return 0; … Read more
You can use the core with GDB in many ways, but passing parameters which is to be passed to the executable to GDB is not the way to use the core file. This could also be the reason you got that error. You can use the core file in the following ways: gdb <executable> <core-file> … Read more
What happens when a core file is generated from a Linux distro other than the one we are running in Dev? Is the stack trace even meaningful? It the executable is dynamically linked, as yours is, the stack GDB produces will (most likely) not be meaningful. The reason: GDB knows that your executable crashed by … Read more
watch only breaks on write, rwatch let you break on read, and awatch let you break on read/write. You can set read watchpoints on memory locations: gdb$ rwatch *0xfeedface Hardware read watchpoint 2: *0xfeedface but one limitation applies to the rwatch and awatch commands; you can’t use gdb variables in expressions: gdb$ rwatch $ebx+0xec1a04f Expression … Read more
Via gdb: (gdb) attach process_id (gdb) call putenv (“env_var_name=env_var_value”) (gdb) detach This is quite a nasty hack and should only be done in the context of a debugging scenario, of course.