Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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 14:52:00 -0000	[thread overview]
Message-ID: <20170119145152.GA6289@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:
> > Hi,
> > 
> > I'm attempting to convert CGDB (a GDB front end) from annotations to MI.
> > Two questions I've run up against:
> > 
> > The first is, with annotations, it's easy to tell when GDB can except
> > another command, just wait for the prompt annotation.
> > With GDB/MI it seems a little trickier. So far I have this:
> >     Wait for the gdb prompt
> >     If you have not recieved a *running yet, it's safe to run a command.
> >     Otherwise, if you have recieved a *running, you need to wait for
> >     the prompt and for *stopped.
> > Anyone have a better approach? Does multi target impact this?
> 
> In most cases, you don't need to care about this.  You can normally
> send other commands even when GDB is blocked and they will be
> buffered until GDB unblocks.

I understand that your opinion is to just send the commands and let them
buffer. However, it avoids the question. Is there a technique to know
if GDB is ready for input using MI?

Thanks,
Bob Rossi


  reply	other threads:[~2017-01-19 14:52 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 [this message]
2017-01-19 15:06     ` Pedro Alves
2017-01-19 15:11   ` Bob Rossi
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=20170119145152.GA6289@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