Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: [RFA] Announce mi pending breakpoint support.
Date: Sun, 16 Dec 2007 21:33:00 -0000	[thread overview]
Message-ID: <200712170028.17907.ghost@cs.msu.su> (raw)


This patch makes the -list-features command announce presence
of the recently committed support for pending breakpoints in MI.
I need it to automatically make use of this functionality in
KDevelop 3.5. OK?

- Volodya

	gdb/
	* mi/mi-main.c (mi_cmd_list_features): Announce
	the 'pending-breakpoints' feature.

	gdb/doc/
	* gdb.texinfo (Miscellaneous gdb/mi Commands):
	Document 'pending-breakpoints' feature of
	-list-features.
---
 gdb/doc/gdb.texinfo |    4 ++++
 gdb/mi/mi-main.c    |    1 +
 2 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 01f5db5..db4106e 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -21600,6 +21600,10 @@ The current list of features is:
 @samp{frozen-varobjs}---indicates presence of the
 @code{-var-set-frozen} command, as well as possible presense of the
 @code{frozen} field in the output of @code{-varobj-create}.
+@item
+@samp{pending-breakpoints}---indicates presence of the @code{-f}
+option to the @code{-break-insert} command.
+
 @end itemize
 
 @subheading The @code{-interpreter-exec} Command
diff --git a/gdb/mi/mi-main.c b/gdb/mi/mi-main.c
index 025c66d..b23d337 100644
--- a/gdb/mi/mi-main.c
+++ b/gdb/mi/mi-main.c
@@ -1054,6 +1054,7 @@ mi_cmd_list_features (char *command, char **argv, int argc)
       cleanup = make_cleanup_ui_out_list_begin_end (uiout, "features");      
 
       ui_out_field_string (uiout, NULL, "frozen-varobjs");
+      ui_out_field_string (uiout, NULL, "pending-breakpoints");
       
       do_cleanups (cleanup);
 
-- 
1.5.3.5


             reply	other threads:[~2007-12-16 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 21:33 Vladimir Prus [this message]
2007-12-16 22:07 ` Daniel Jacobowitz

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=200712170028.17907.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --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