Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Alain Magloire" <alain@qnx.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC] -mi-level command
Date: Wed, 07 May 2003 18:34:00 -0000	[thread overview]
Message-ID: <200305071834.OAA22796@node1.ott.qnx.com> (raw)

Bonjour

	Maybe there is a better way to do this, most clients of GDB/MI
need a way to know the level to adjust the parsing or go around bugs in
previous(or current version).

	One problem with the code below is that mi_version() is returning ..."3"

I'll be happy to provide docs etc .. after.
8<---8<---------------------------------------
Index: mi-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-cmds.c,v
retrieving revision 1.12
diff -u -r1.12 mi-cmds.c
--- mi-cmds.c	4 May 2003 03:50:13 -0000	1.12
+++ mi-cmds.c	7 May 2003 18:24:34 -0000
@@ -96,6 +96,7 @@
   {"kod-list", 0, 0},
   {"kod-list-object-types", 0, 0},
   {"kod-show", 0, 0},
+  {"mi-level", 0, 0, mi_cmd_mi_level},
   {"overlay-auto", 0, 0},
   {"overlay-list-mapping-state", 0, 0},
   {"overlay-list-overlays", 0, 0},
Index: mi-cmds.h
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-cmds.h,v
retrieving revision 1.9
diff -u -r1.9 mi-cmds.h
--- mi-cmds.h	4 May 2003 03:50:13 -0000	1.9
+++ mi-cmds.h	7 May 2003 18:24:34 -0000
@@ -81,6 +81,7 @@
 extern mi_cmd_args_ftype mi_cmd_exec_until;
 extern mi_cmd_args_ftype mi_cmd_exec_interrupt;
 extern mi_cmd_argv_ftype mi_cmd_file_list_exec_source_file;
+extern mi_cmd_argv_ftype mi_cmd_mi_level;
 extern mi_cmd_argv_ftype mi_cmd_gdb_exit;
 extern mi_cmd_argv_ftype mi_cmd_interpreter_exec;
 extern mi_cmd_argv_ftype mi_cmd_stack_info_depth;
Index: mi-main.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-main.c,v
retrieving revision 1.43
diff -u -r1.43 mi-main.c
--- mi-main.c	5 May 2003 17:56:57 -0000	1.43
+++ mi-main.c	7 May 2003 18:24:34 -0000
@@ -109,6 +109,13 @@
    formalized. */
 
 enum mi_cmd_result
+mi_cmd_mi_level (char *command, char **argv, int argc)
+{
+   ui_out_field_int (uiout, "level", mi_version(uiout));
+   return MI_CMD_DONE;
+}
+
+enum mi_cmd_result
 mi_cmd_gdb_exit (char *command, char **argv, int argc)
 {
   /* We have to print everything right here because we never return */


             reply	other threads:[~2003-05-07 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 18:34 Alain Magloire [this message]
2003-05-07 19:40 ` Andrew Cagney
2003-05-07 20:28   ` Alain Magloire
2003-06-22 18:15     ` Andrew Cagney

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=200305071834.OAA22796@node1.ott.qnx.com \
    --to=alain@qnx.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