From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1161 invoked by alias); 11 May 2006 06:39:34 -0000 Received: (qmail 1151 invoked by uid 22791); 11 May 2006 06:39:34 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 11 May 2006 06:39:32 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 89C8948CE79 for ; Thu, 11 May 2006 02:39:30 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13444-01-3 for ; Thu, 11 May 2006 02:39:30 -0400 (EDT) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id 4186B48CDF6 for ; Thu, 11 May 2006 02:39:30 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 8E48747E7F; Wed, 10 May 2006 23:39:29 -0700 (PDT) Date: Thu, 11 May 2006 10:24:00 -0000 From: Joel Brobecker To: gdb@sources.redhat.com Subject: Re: CLI commands in MI Message-ID: <20060511063929.GE27212@adacore.com> References: <20060511022650.GA3727@brasko.net> <20060511034114.GA25755@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060511034114.GA25755@nevyn.them.org> User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00124.txt.bz2 > Now, if we look at the command set someday (around mi4 maybe), and find > that it's become complete, then perhaps we can disable the CLI hack. How about if the front-end wants to provide a debugger console, so that the user can also enter commands manually? I would have hoped that we could still allow the user to use CLI commands in that console, because MI commands output are somewhat difficult to read for a normal human. Basically, the front-end would take the user command in CLI format, send it to the MI interpreter via this feature, and then get the output back, extract it from the MI output, and then display it on the console. Is there another way of doing this? -- Joel