I am trying to explore gdb, objdump, valgrind and nm tools for debugging purpose in linux.
I am able to print local variables using info locals in GDB but I need to go into current stack frame to print local variables.
Is there any way to print all the local and global variables (with values) used in a C code (maybe from a coredump if program is crashed) without going into particular stack frame?
As you pointed out, in gdb you can show the local variables for the current frame with info locals. If your restriction is that you don't want to manually go into each frame, then you can use a simple gdb script that does that for you. For example:
define locals-up
set $n = ($arg0)
set $upto = $n
while $upto > 0
info locals
up-silently 1
set $upto = $upto - 1
end
down-silently $n
end
document locals-up
locals-up <n>: Lists local variables of n frames
end
Well no, since you have to analyze the stack in order to figure out which local variables even exist.
If you have a a function:
static int foo(int a, int b, int c)
{
const int ab = a + b;
const int bc = b + c;
return ab * bc;
}
you can't talk about "the local variables of foo()" unless you have a stack frame that indicates that foo() is running. Otherwise, the local variables won't exist: they're allocated on the stack as the function is entered, after all.
Of course, there could be a "clever" command to walk up the stack from a given breakpoint's frame and print all encountered functions' local variables, but that doesn't sound like what you're after.
