From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: NEWS update
Date: Tue, 17 Aug 2010 18:33:00 -0000 [thread overview]
Message-ID: <m3k4npgkck.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83zkwlqf27.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 17 Aug 2010 21:17:36 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> Can the entry elaborate a bit more about this? I'm afraid I was
Eli> unable to understand what will the improvement mean to me as a C++
Eli> programmer. "Puts template parameter in scope" is somewhat cryptic,
Eli> IMO.
Sure. How about this?
Tom
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.399
diff -u -c -r1.399 NEWS
cvs diff: conflicting specifications of output style
Write failed flushing stdout buffer.
write stdout: Broken pipe
*** NEWS 16 Aug 2010 21:19:29 -0000 1.399
--- NEWS 17 Aug 2010 18:33:05 -0000
***************
*** 12,17 ****
--- 12,28 ----
result = some_value (10,20)
+ * C++ Improvements:
+
+ ** GDB now puts template parameters in scope when debugging in an
+ instantiation. For example, if you have:
+
+ template<int X> int func (void) { return X; }
+
+ Then if you step into func<5>, "print X" will show "5". This
+ feature requires proper debuginfo support from the compiler; it
+ was added to GCC 4.5.
+
* GDB now has some support for using labels in the program's source in
linespecs. For instance, you can use "advance label" to continue
execution to a label.
next prev parent reply other threads:[~2010-08-17 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 17:15 Tom Tromey
2010-08-17 18:19 ` Eli Zaretskii
2010-08-17 18:33 ` Tom Tromey [this message]
2010-08-17 19:25 ` Eli Zaretskii
2010-08-17 21:33 ` Tom Tromey
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=m3k4npgkck.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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