When I use gdb to debug, it is not getting the correct addresses for
local variables, and thus showing bogus information.  For example,
if a set a break on a function, and step into it, and print the argument name, e.g. foo(int x) { int y; blah(x); y = x + 1; }
print x or y, it comes up with bogus values.

I'm not sure when gdb started doing this, I recall it didn't before,
it's been doing it a while now, and frankly, I just make variables global which gdb gets right, but that is a poor workaround, and I'm
getting frustrated.  gdb reports version 5.1.1, mspgcc is version 3.3

I appreciate any assistance.

-Kelly Murray


Reply via email to