Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [MI/RFC] Emit ^running via observer.
Date: Sun, 29 Jun 2008 02:40:00 -0000	[thread overview]
Message-ID: <18534.53828.605142.257614@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200806281348.44175.vladimir@codesourcery.com>

 > I still don't understand what you mean by "decouples the output from the
 > input".  GDB, both in sync and async mode is in perfect position to print
 > things as it sees fit. And MI notifications don't actually care about
 > 'current interpreter'. The *only* fundamental limitation of sync mode is
 > that no command will be processed when the target is running. Am I missing
 > something?

I think we're saying similar things.  You're saying that sync mode should
be able to generate MI output from CLI commands like "run", "next" etc.  I'm
just saying that I don't know how to do it and it's probably quite messy.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


      reply	other threads:[~2008-06-29  0:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 22:01 Vladimir Prus
2008-06-20  6:53 ` Nick Roberts
2008-06-25 15:04   ` Vladimir Prus
2008-06-26 13:33     ` Nick Roberts
2008-06-26 18:54       ` Vladimir Prus
2008-06-26 19:34         ` Daniel Jacobowitz
2008-06-28 11:34           ` Vladimir Prus
2008-06-28 16:35             ` Vladimir Prus
2008-06-27  6:58         ` Nick Roberts
2008-06-27 11:58           ` Vladimir Prus
2008-06-28  5:49             ` Nick Roberts
2008-06-28  9:41               ` Vladimir Prus
2008-06-28 10:16                 ` Nick Roberts
2008-06-28 10:44                   ` Vladimir Prus
2008-06-29  2:40                     ` Nick Roberts [this message]

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=18534.53828.605142.257614@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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