This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [MI/RFC] Emit ^running via observer.

From: Nick Roberts <nickrob at snap dot net dot nz>
To: Vladimir Prus <vladimir at codesourcery dot com>
Cc: gdb-patches at sources dot redhat dot com
Date: Sun, 29 Jun 2008 12:07:32 +1200
Subject: Re: [MI/RFC] Emit ^running via observer.
References: <200806140108.24047.vladimir@codesourcery.com> <200806280949.09304.vladimir@codesourcery.com> <18534.1805.519374.851454@kahikatea.snap.net.nz> <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

References:
- [MI/RFC] Emit ^running via observer.
  - From: Vladimir Prus
- Re: [MI/RFC] Emit ^running via observer.
  - From: Vladimir Prus
- Re: [MI/RFC] Emit ^running via observer.
  - From: Nick Roberts
- Re: [MI/RFC] Emit ^running via observer.
  - From: Vladimir Prus

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]