Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@redhat.com
Subject: RFA: mark -enable-pretty-printing as experimental (Was: Patch: implement new dynamic varobj spec)
Date: Wed, 16 Sep 2009 23:52:00 -0000	[thread overview]
Message-ID: <m3hbv2pv9e.fsf_-_@fleche.redhat.com> (raw)
In-Reply-To: <h8ptv2$4sm$3@ger.gmane.org> (Vladimir Prus's message of "Wed, 16 	Sep 2009 09:44:06 +0400")

>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:

Volodya> I think it makes sense. You list 3 known issues in the original
Volodya> email, and while I hope we'll fix them by 7.0, there will be
Volodya> just too little time for extensive testing. Let's keep our
Volodya> options open for a bit more.

How about this?

Tom

2009-09-16  Tom Tromey  <tromey@redhat.com>

	* gdb.texinfo (GDB/MI Variable Objects): -enable-pretty-printing
	is experimental.

cvs diff: Diffing .
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.624
diff -u -c -r1.624 gdb.texinfo
cvs diff: conflicting specifications of output style
Write failed flushing stdout buffer.
write stdout: Broken pipe
*** gdb.texinfo	15 Sep 2009 18:51:25 -0000	1.624
--- gdb.texinfo	16 Sep 2009 19:02:55 -0000
***************
*** 23547,23552 ****
--- 23547,23555 ----
  Note that if Python support has not been compiled into @value{GDBN},
  this command will still succeed (and do nothing).
  
+ This feature is currently experimental, and may work differently in
+ future versions of @value{GDBN}.
+ 
  @subheading The @code{-var-create} Command
  @findex -var-create
  


  reply	other threads:[~2009-09-16 23:52 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10 20:58 Patch: implement new dynamic varobj spec Tom Tromey
2009-09-11  5:41 ` Nick Roberts
2009-09-11 19:41   ` Tom Tromey
2009-09-11 20:49     ` Eli Zaretskii
2009-09-11 21:12       ` Tom Tromey
2009-09-12  8:08         ` Eli Zaretskii
2009-09-11 23:55     ` Nick Roberts
2009-09-14 19:59       ` Tom Tromey
2009-09-14 22:55         ` Nick Roberts
2009-09-15 15:37           ` Tom Tromey
2009-09-15 22:28             ` Nick Roberts
2009-09-16  5:45               ` Vladimir Prus
2009-09-16  9:56                 ` Nick Roberts
2009-09-16 17:12               ` Tom Tromey
2009-09-16 22:26                 ` Nick Roberts
2009-09-15 22:43             ` Nick Roberts
2009-09-16  5:39               ` Vladimir Prus
2009-09-16  9:36                 ` Nick Roberts
2009-09-16  5:44         ` Vladimir Prus
2009-09-16 23:52           ` Tom Tromey [this message]
     [not found]             ` <h8vk80$fqc$2@ger.gmane.org>
2009-09-18 10:02               ` RFA: mark -enable-pretty-printing as experimental (Was: Patch: implement new dynamic varobj spec) Eli Zaretskii
2009-09-18 18:01                 ` RFA: mark -enable-pretty-printing as experimental Tom Tromey
2009-09-14 19:56   ` Patch: implement new dynamic varobj spec Tom Tromey
2009-09-12  9:18 ` Eli Zaretskii
2009-09-14 20:03   ` Tom Tromey
2009-09-14 20:22     ` Eli Zaretskii
2009-09-14 21:29       ` Tom Tromey
2009-09-15  3:06         ` Eli Zaretskii
2009-09-14 11:24 ` Vladimir Prus
2009-09-16 23:53   ` Tom Tromey
2009-09-16  5:46     ` Vladimir Prus
2009-09-19 12:01     ` Matt Rice
2009-09-19 15:59       ` Joel Brobecker
2009-09-14 20:05 ` Tom Tromey
2009-09-14 20:24   ` Eli Zaretskii
2009-09-14 23:58   ` Nick Roberts
2009-09-18  9:29 ` Vladimir Prus
2009-09-18 18:25   ` Tom Tromey
2009-09-19 12:57   ` Vladimir Prus

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=m3hbv2pv9e.fsf_-_@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@redhat.com \
    --cc=vladimir@codesourcery.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