From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Implement -exec-jump
Date: Wed, 08 Apr 2009 05:50:00 -0000 [thread overview]
Message-ID: <200904080950.16691.vladimir@codesourcery.com> (raw)
This patch, committed, implements the -exec-jump MI command.
(Documentation follows later)
- Volodya
Index: gdb/ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.10357
diff -u -p -r1.10357 ChangeLog
--- gdb/ChangeLog 5 Apr 2009 22:37:19 -0000 1.10357
+++ gdb/ChangeLog 8 Apr 2009 05:48:34 -0000
@@ -1,3 +1,11 @@
+2009-04-08 Vladimir Prus <vladimir@codesourcery.com>
+
+ Implement -exec-jump.
+
+ * mi/mi-cmds.h (mi_cmd_exec_jump): Declare.
+ * mi/mi-main.c (mi_cmd_exec_jump): New.
+ * mi/mi-cmds.c (mi_cmds): Register exec-jump.
+
2009-04-06 Mark Kettenis <kettenis@gnu.org>
* sparc64nbsd-nat.c (sparc64nbsd_supply_pcb): Fix comment.
Index: gdb/mi/mi-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-cmds.c,v
retrieving revision 1.38
diff -u -p -r1.38 mi-cmds.c
--- gdb/mi/mi-cmds.c 3 Jan 2009 05:57:57 -0000 1.38
+++ gdb/mi/mi-cmds.c 8 Apr 2009 05:48:34 -0000
@@ -61,6 +61,7 @@ struct mi_cmd mi_cmds[] =
{ "exec-arguments", { "set args", 1 }, NULL },
{ "exec-continue", { NULL, 0 }, mi_cmd_exec_continue},
{ "exec-finish", { NULL, 0 }, mi_cmd_exec_finish},
+ { "exec-jump", { NULL, 0 }, mi_cmd_exec_jump},
{ "exec-interrupt", { NULL, 0 }, mi_cmd_exec_interrupt},
{ "exec-next", { NULL, 0 }, mi_cmd_exec_next},
{ "exec-next-instruction", { NULL, 0 }, mi_cmd_exec_next_instruction},
Index: gdb/mi/mi-cmds.h
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-cmds.h,v
retrieving revision 1.36
diff -u -p -r1.36 mi-cmds.h
--- gdb/mi/mi-cmds.h 3 Jan 2009 05:57:57 -0000 1.36
+++ gdb/mi/mi-cmds.h 8 Apr 2009 05:48:34 -0000
@@ -53,6 +53,7 @@ extern mi_cmd_argv_ftype mi_cmd_env_path
extern mi_cmd_argv_ftype mi_cmd_env_pwd;
extern mi_cmd_argv_ftype mi_cmd_exec_continue;
extern mi_cmd_argv_ftype mi_cmd_exec_finish;
+extern mi_cmd_argv_ftype mi_cmd_exec_jump;
extern mi_cmd_argv_ftype mi_cmd_exec_next;
extern mi_cmd_argv_ftype mi_cmd_exec_next_instruction;
extern mi_cmd_argv_ftype mi_cmd_exec_return;
Index: gdb/mi/mi-main.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-main.c,v
retrieving revision 1.146
diff -u -p -r1.146 mi-main.c
--- gdb/mi/mi-main.c 25 Mar 2009 21:42:35 -0000 1.146
+++ gdb/mi/mi-main.c 8 Apr 2009 05:48:34 -0000
@@ -168,6 +168,13 @@ mi_cmd_exec_return (char *command, char
print_stack_frame (get_selected_frame (NULL), 1, LOC_AND_ADDRESS);
}
+void
+mi_cmd_exec_jump (char *args, char **argv, int argc)
+{
+ /* FIXME: Should call a libgdb function, not a cli wrapper. */
+ return mi_execute_async_cli_command ("jump", argv, argc);
+}
+
static int
proceed_thread_callback (struct thread_info *thread, void *arg)
{
next reply other threads:[~2009-04-08 5:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 5:50 Vladimir Prus [this message]
2009-04-08 6:55 ` Eli Zaretskii
2009-04-08 7:08 ` Vladimir Prus
2009-04-08 7:22 ` Eli Zaretskii
2009-04-08 7:36 ` Vladimir Prus
2009-04-08 9:00 ` Eli Zaretskii
2009-04-08 16:26 ` Tom Tromey
2009-04-22 12:57 ` Vladimir Prus
2009-04-22 17:26 ` Eli Zaretskii
2009-04-08 9:16 ` André Pönitz
2009-04-08 9:29 ` Eli Zaretskii
2009-04-08 11:05 ` André Pönitz
2009-04-08 11:46 ` Eli Zaretskii
2009-04-08 21:51 ` Thiago Jung Bauermann
2009-04-08 21:57 ` Joel Brobecker
2009-04-10 16:50 ` Eli Zaretskii
2009-04-13 17:24 ` Tom Tromey
2009-04-08 16:28 ` Tom Tromey
2009-04-08 22:03 ` Thiago Jung Bauermann
2009-04-22 12:09 ` Vladimir Prus
2009-04-22 17:16 ` Eli Zaretskii
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=200904080950.16691.vladimir@codesourcery.com \
--to=vladimir@codesourcery.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