From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com, mec.gnu@mindspring.com
Cc: carlton@kealia.com, gdb-patches@sources.redhat.com, vinschen@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: <20040309152736.ADE394B104@berman.michael-chastain.com> (raw)
mec> Is it okay for gcc to emit debug info that "i" is out of scope here?
drow> I think so. It's unfortunate.
Okay, that makes three people in favor of accepting this limited
scoping from gcc 3.4, good enough for me.
drow> Duplicate the file, then, since we've decided this is a bad practice?
You're right, this is better.
I was secretly hoping not to touch misc.cc at all, because as soon as I
go to touch it, I have to add a proper copyright notice, and then
re-test with all the *.exp anyways.
I'd better get to work.
Michael C
WARNING: multiple messages have this Message-ID
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com, mec.gnu@mindspring.com
Cc: carlton@kealia.com, gdb-patches@sources.redhat.com, vinschen@redhat.com
Subject: Re: [RFC/RFA] gdb.cp/classes.exp: Don't try to print local variable out of scope
Date: Tue, 09 Mar 2004 15:27:00 -0000 [thread overview]
Message-ID: <20040309152736.ADE394B104@berman.michael-chastain.com> (raw)
Message-ID: <20040309152700.iN6FxCwJxXBpNCog9TEZMCbVL87ckRnelRS6EFGZs7M@z> (raw)
mec> Is it okay for gcc to emit debug info that "i" is out of scope here?
drow> I think so. It's unfortunate.
Okay, that makes three people in favor of accepting this limited
scoping from gcc 3.4, good enough for me.
drow> Duplicate the file, then, since we've decided this is a bad practice?
You're right, this is better.
I was secretly hoping not to touch misc.cc at all, because as soon as I
go to touch it, I have to add a proper copyright notice, and then
re-test with all the *.exp anyways.
I'd better get to work.
Michael C
next reply other threads:[~2004-03-09 15:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Michael Elizabeth Chastain [this message]
2004-03-09 15:27 ` Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
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-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 Michael Elizabeth Chastain
2004-03-09 15:11 ` Michael Elizabeth Chastain
2004-03-09 15:40 ` Corinna Vinschen
2004-03-19 0:09 ` Corinna Vinschen
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-09 15:20 ` Daniel Jacobowitz
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 23:58 ` Michael Elizabeth Chastain
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=20040309152736.ADE394B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vinschen@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