From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Cc: Daniel Jacobowitz <drow@mvista.com>
Subject: [patch/rfc] mention C++ support in NEWS
Date: Wed, 11 Feb 2004 18:15:00 -0000 [thread overview]
Message-ID: <m3vfmdo534.fsf@coconut.kealia.com> (raw)
I'm pretty much done merging in my C++ changes (I'll post another
message with more details in a sec), so it seems like it's time to
mention it in NEWS. Any suggested improvements to the wording in the
following patch?
David Carlton
carlton@kealia.com
2004-02-11 David Carlton <carlton@kealia.com>
* NEWS: Mention C++ nested types and namespaces.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.135
diff -u -p -r1.135 NEWS
--- NEWS 5 Feb 2004 19:56:33 -0000 1.135
+++ NEWS 11 Feb 2004 18:10:42 -0000
@@ -36,6 +36,13 @@ GDB support for location expressions has
arguments and frame bases. Older versions of GDB could crash when they
encountered these.
+* C++ nested types and namespaces
+
+GDB's support for nested types and namespaces in C++ has been
+improved. We recommend that you use the DWARF 2 debugging format to
+get the full benefit from this; this is the default for recent
+versions of GCC on most platforms.
+
* New native configurations
NetBSD/amd64 x86_64-*-netbsd*
next reply other threads:[~2004-02-11 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 18:15 David Carlton [this message]
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 ` David Carlton
2004-03-17 17:39 ` David Carlton
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-17 1:29 Michael Elizabeth Chastain
2004-03-19 0:09 ` 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=m3vfmdo534.fsf@coconut.kealia.com \
--to=carlton@kealia.com \
--cc=drow@mvista.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