From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] gdb.cp/classes.exp: Don't try to print local variable out of scope
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040309154019.GA24481@cygbert.vinschen.de> (raw)
Message-ID: <20040319000900.S6AwpwEtJZeSTf9mNmJQgz7dBYHJ3eLNldvfCffrU4I@z> (raw)
In-Reply-To: <20040309151111.DE3094B104@berman.michael-chastain.com>
Hi Michael,
On Mar 9 10:11, Michael Elizabeth Chastain wrote:
> 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.
basically this problem is similar to the "having the same variable
defined twice in a function" problem:
1 void foo ()
2 {
3 int i = 1;
4 {
5 int i = 2;
6 bar(i);
7 }
8 bar (i);
9 }
Is line 7 still in the scope of the inner definition of variable `i'?
Which `i' should be printed at that point?
> 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?
IMHO yes. Keep in mind that it's a *local* variable. It's practically
dead at this point. $pc sits already in the epilogue which destroys the
variable anyway. Just one `stepi' would perhaps *really* destroy the
variable and GDB might print some entirely confused value.
> cv> I'd suggest to change the testsuite case to add another line to the
> cv> function enums1(), so that it's sure to be still in the scope of the
> cv> local variable obj_with_enum.
>
> 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.
I tested the whole gdb.cp testsuite on linux-x-sh with and without the
patch and the only difference in the testsuite output where the tests
directly affected by this change:
7c7,10
< (gdb) KFAIL: gdb.cp/classes.exp: ptype obj_with_enum (PRMS: gdb/57)
---
> (gdb) FAIL: gdb.cp/classes.exp: print obj_with_enum (2)
> (gdb) FAIL: gdb.cp/classes.exp: print obj_with_enum.priv_enum
> (gdb) FAIL: gdb.cp/classes.exp: ptype obj_with_enum.priv_enum
> (gdb) FAIL: gdb.cp/classes.exp: ptype obj_with_enum
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
next prev parent reply other threads:[~2004-03-09 15:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-09 15:11 ` Michael Elizabeth Chastain
2004-03-09 15:40 ` Corinna Vinschen [this message]
2004-03-19 0:09 ` Corinna Vinschen
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-09 15:20 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-09 15:27 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-10 23:58 ` Michael Elizabeth Chastain
2004-03-19 0:09 Corinna Vinschen
2004-03-09 13:00 ` Corinna Vinschen
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-09 14:17 ` Daniel Jacobowitz
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-10 2:06 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-09 16:15 ` Michael Elizabeth Chastain
2004-03-19 0:09 ` Andrew Cagney
2004-03-09 20:38 ` Andrew Cagney
2004-03-09 21:27 ` Daniel Jacobowitz
2004-03-09 22:32 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-10 0:56 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-10 1:51 ` Andrew Cagney
2004-03-10 3:05 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-10 3:23 ` Daniel Jacobowitz
2004-03-10 22:21 ` Andrew Cagney
2004-03-10 22:29 ` Daniel Jacobowitz
2004-03-15 18:47 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040309154019.GA24481@cygbert.vinschen.de \
--to=vinschen@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox