gdb with gcj
Andrew Haley
aph@redhat.com
Sat May 1 17:53:00 GMT 2004
Bryce McKinlay writes:
> > > Well, it's been like that for a long while, and AFAIK it's a hard
> > problem. In theory you can generate DWARF expressions that allow
> > you to calculate what a variable would be if the code were not
> > optimized, but in the general case it's impossible. After all,
> > the "as if" rule allows the compiler completely to rewrite a
> > program.
>
> Sure, I guess its reasonable to expect that with optimization, you
> won't always get entirely accurate/reliable output when printing
> local variables. This is how it used to work. But, the problem I
> see now is that GDB basically refuses to print local variables at
> all. It doesn't even try - it just says the variables don't
> exist. So in this respect the problem has become significantly
> worse in recent months.
Okay, we might be talking about totally different things.
I agree that a PR seems in order. I am working on fixing some
unrelated debug info bugs at the moment, so I guess I'll look at this
problem while I've got the lid off.
Andrew.
More information about the Java
mailing list