This is the mail archive of the gdb@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 Development

From: Vladimir Prus <ghost at cs dot msu dot su>
To: Nick Roberts <nickrob at snap dot net dot nz>
Cc: gdb at sources dot redhat dot com
Date: Wed, 5 Sep 2007 09:40:18 +0400
Subject: Re: MI Development
References: <200709041740.22271.ghost@cs.msu.su> <18142.16140.486009.379849@kahikatea.snap.net.nz>

On Wednesday 05 September 2007 09:30:52 Nick Roberts wrote:
>  > CLI commands bypass MI When a CLI command is issued, we don't see
>  > "^running". As result, frontend can easily think that gdb is waiting for
>  > commands while inferior is running.
> 
> With asynchronous operation, asynchronous CLI commands give the same MI output
> that MI commands do.

Why would I want to enable asynchronous operation for that to work? The
default behaviour is just broken, so even if --async fixes that, we should not
require any switches to get non-broken behaviour.

- Volodya

Follow-Ups:
- Re: MI Development
  - From: Nick Roberts

References:
- MI Development
  - From: Vladimir Prus
- Re: MI Development
  - From: Nick Roberts

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