From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: carlton@kealia.com, eliz@elta.co.il
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] mention C++ support in NEWS
Date: Wed, 17 Mar 2004 01:29:00 -0000 [thread overview]
Message-ID: <20040317012833.08EC64B104@berman.michael-chastain.com> (raw)
That's a good point. How about:
GDB's support for nested types and namespaces in C++ has been
improved, especially if you use the DWARF 2 debugging format. (This
is the default for recent versions of GCC on most platforms.)
Specifically, if you have a class "Inner" defined within a class or
namespace "Outer", then GDB realizes that the class's name is
"Outer::Inner", not simply "Inner". This should greatly reduce the
frequency of complaints about not finding RTTI symbols. In
addition, if you are stopped at inside of a function defined within
a namespace, GDB modifies its name lookup accordingly.
My two cents: looks okay to me.
Michael C
WARNING: multiple messages have this Message-ID
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: carlton@kealia.com, eliz@elta.co.il
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] mention C++ support in NEWS
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040317012833.08EC64B104@berman.michael-chastain.com> (raw)
Message-ID: <20040319000900.hDN6xDMzqUYkTigW_NSYY4MlV56C_QqX7VlZfjBqeIY@z> (raw)
That's a good point. How about:
GDB's support for nested types and namespaces in C++ has been
improved, especially if you use the DWARF 2 debugging format. (This
is the default for recent versions of GCC on most platforms.)
Specifically, if you have a class "Inner" defined within a class or
namespace "Outer", then GDB realizes that the class's name is
"Outer::Inner", not simply "Inner". This should greatly reduce the
frequency of complaints about not finding RTTI symbols. In
addition, if you are stopped at inside of a function defined within
a namespace, GDB modifies its name lookup accordingly.
My two cents: looks okay to me.
Michael C
next reply other threads:[~2004-03-17 1:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 1:29 Michael Elizabeth Chastain [this message]
2004-03-19 0:09 ` Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
2004-02-11 18:15 David Carlton
2004-02-11 19:31 ` Eli Zaretskii
2004-02-16 19:44 ` Daniel Jacobowitz
2004-03-19 0:09 ` David Carlton
2004-03-17 0:29 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-17 6:11 ` Eli Zaretskii
2004-03-17 17:32 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` David Carlton
2004-03-17 17:39 ` David Carlton
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=20040317012833.08EC64B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=eliz@elta.co.il \
--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