From: Bob Rossi <bob@brasko.net>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB/MI questions
Date: Thu, 19 Jan 2017 15:11:00 -0000 [thread overview]
Message-ID: <20170119151120.GB6289@xubuntu.brasko.net> (raw)
In-Reply-To: <DB4PR07MB0656CEBBCC14BB061FB319B6F57E0@DB4PR07MB0656.eurprd07.prod.outlook.com>
On Thu, Jan 19, 2017 at 02:30:58PM +0000, Marc Khouzam wrote:
> > Second, from the CLI if you run the command "next", then if you hit
> > the enter key, GDB will run the "next" command again.
> > However, in GDB/MI if you run -interpreter-exec console "next", and then
> > follow that with the Enter key, GDB does nothing.
> > Is there a way to run the last command?
...
> But if you really want that for some reason, you can just keep track
> of the last command you sent in MI, and then when getting an lone
> Enter, you could send it again. But then you don't have the smarts
> of GDB to know which commands should repeat and which should not.
> I don't think this is a very good idea.
I'm just trying to provide the same functionality I did when I was using
annotations. This was one of the noted differences.
Since the MI differs in this area, I've done as you suggested and
that works well. I guess I'll see if there are any downsides here.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2017-01-19 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170119031445.GA24616@xubuntu.brasko.net>
2017-01-19 14:31 ` Marc Khouzam
2017-01-19 14:52 ` Bob Rossi
2017-01-19 15:06 ` Pedro Alves
2017-01-19 15:11 ` Bob Rossi [this message]
2017-01-19 15:24 ` Marc Khouzam
2017-01-19 15:40 ` Jan Vrany
2017-01-19 16:17 ` Pedro Alves
2017-01-19 15:47 ` Simon Marchi
2017-01-19 16:03 ` Bob Rossi
2017-01-19 16:15 ` Simon Marchi
2017-01-19 16:27 ` Bob Rossi
2017-01-19 16:33 ` Pedro Alves
2017-01-19 14:43 ` Pedro Alves
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=20170119151120.GB6289@xubuntu.brasko.net \
--to=bob@brasko.net \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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