From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23555 invoked by alias); 10 Mar 2005 17:52:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 23459 invoked from network); 10 Mar 2005 17:52:47 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 10 Mar 2005 17:52:47 -0000 Received: from drow by nevyn.them.org with local (Exim 4.44 #1 (Debian)) id 1D9Rpt-0002GW-3f; Thu, 10 Mar 2005 12:52:37 -0500 Date: Thu, 10 Mar 2005 17:52:00 -0000 From: Daniel Jacobowitz To: Dave Korn , 'Karganov Konstantin' , 'GDB' Subject: Re: MI output command error Message-ID: <20050310175236.GA8276@nevyn.them.org> Mail-Followup-To: Dave Korn , 'Karganov Konstantin' , 'GDB' References: <20050310144013.GB14061@white> <20050310160852.GC14061@white> <20050310161309.GA14175@nevyn.them.org> <20050310174408.GE14061@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050310174408.GE14061@white> User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00117.txt.bz2 On Thu, Mar 10, 2005 at 12:44:08PM -0500, Bob Rossi wrote: > Hi Daniel, > > The whole idea of GDB being asyncronous is new to me. Up until now, I > have been very content thinking that GDB would become "busy" whenver the > inferior was started up to do some work. > > I would really like to understand the concept and the reason why GDB had > to have the asyncronous feature. While looking for documentation on GDB > being asyncronous, I've only found very little. A grep of gdb.texino > yeilded me nothing interesting. Sorry, I don't know anything more about async mode than is in the documentation (and mailing list archives - it has come up plenty of times). It shouldn't take much thinking to understand why asynchronous operation is desirable. A user interface is _always_ asynchronous, because your human user never blocks. I'm as mystified as Dave as to how you could read the manual and believe GDB/MI was designed to operate synchronously. A number of MI commands have documentation that begins with "Asynchronous command." In particular, look at -exec-interrupt, which makes no sense as a synchronous command. > I noticed that the command line option is not documented in the manual. > Which made me think it didn't exist. However, when I run gdb --help, > it's there. > gdb --help > --[no]async Enable (disable) asynchronous version of CLI > > When I try to use the option, it fails, > > $ gdb --async ./main > gdb: unrecognized option `--async' > Use `gdb --help' for a complete list of options. > > $ gdb --noasync ./main > gdb: unrecognized option `--noasync' > Use `gdb --help' for a complete list of options. > > Am I doing something wrong? 2004-07-16 Andrew Cagney * defs.h (event_loop_p): Replace variable declaration with macro, always 1. * main.c (captured_main): Delete options "-async" and "-noasync". (event_loop_p): Delete variable. * NEWS: Mention that "-async" and "-noasync" were removed. He missed --help; please fix that. -- Daniel Jacobowitz CodeSourcery, LLC