From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11563 invoked by alias); 11 Nov 2008 09:18:02 -0000 Received: (qmail 11520 invoked by uid 71); 11 Nov 2008 09:18:01 -0000 Date: Tue, 11 Nov 2008 09:18:00 -0000 Message-ID: <20081111091801.11516.qmail@sourceware.org> To: nobody@sources.redhat.com Cc: gdb-prs@sources.redhat.com, From: Nick Roberts Subject: Re: mi/2551: Missing MI command to do the same as "jump " or "jump
" Reply-To: Nick Roberts Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2008-q4/txt/msg00042.txt.bz2 The following reply was made to PR mi/2551; it has been noted by GNATS. From: Nick Roberts To: dodji@redhat.com Cc: gdb-gnats@sources.redhat.com Subject: Re: mi/2551: Missing MI command to do the same as "jump " or "jump
" Date: Tue, 11 Nov 2008 22:09:12 +1300 > MI should provide the client with a way to jump to a location, just like the commande line interface does with the "jump" command. > > Please note that in that case, the new MI command needs to output an out-of-band record similar to the one that exists for the -exec-next command. Something along the lines of: > *stopped, reason="a-reason", line="8", file,="something.c" > > That is needed to give the client a chance to update its state. That seems reasonable. Does the patch below do what you want? -- Nick http://www.inet.net.nz/~nickrob --- mi-cmds.c 20 Aug 2008 01:05:02 +1200 1.35 +++ mi-cmds.c 11 Nov 2008 22:03:36 +1300 @@ -61,6 +61,7 @@ struct mi_cmd mi_cmds[] = { "exec-continue", { NULL, 0 }, mi_cmd_exec_continue}, { "exec-finish", { NULL, 0 }, mi_cmd_exec_finish}, { "exec-interrupt", { NULL, 0 }, mi_cmd_exec_interrupt}, + { "exec-jump", { "jump", 1 }, NULL}, { "exec-next", { NULL, 0 }, mi_cmd_exec_next}, { "exec-next-instruction", { NULL, 0 }, mi_cmd_exec_next_instruction}, { "exec-return", { NULL, 0 }, mi_cmd_exec_return},