Re: [RFC/RFA] gdb.cp/classes.exp: Don't try to print local variable out of scope

Daniel Jacobowitz
2004-03-09T15:20:42Z

On Tue, Mar 09, 2004 at 10:11:11AM -0500, Michael Chastain wrote:
> Right.
>
> I want to raise the question: is this really a bug in the gdb test suite,
> or is it a bug in gcc?
>
> That is: is a local variable required to exist at the closing brace of a
> function?
>
> I think your answer is "no, it's not required to exist, therefore the
> gdb test suite should change". My answer is "reluctantly, no,
> it's not required to exist"; I don't think the famous gcc -O0
> debug info clause covers this case. I'm curious what drow and
> carlton and other people have to say.
>
> void foo ()
> {
> int i;
> i = 1;
> bar (i);
> }
>
> (gdb) break bar
> (gdb) run
> (gdb) finish
> (gdb) print i
>
> Is it okay for gcc to emit debug info that "i" is out of scope here?

I think so. It's unfortunate.

> misc.cc is used by three *.exp files so I do not want to touch it
> at all, so I am dis-approving your patch. I will write a patch to
> remove the "gdb_test next" in test_enums instead.

Duplicate the file, then, since we've decided this is a bad practice?

--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer