From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1000 invoked by alias); 17 Mar 2008 23:41:28 -0000 Received: (qmail 992 invoked by uid 22791); 17 Mar 2008 23:41:27 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 17 Mar 2008 23:40:54 +0000 Received: from kahikatea.snap.net.nz (89.30.255.123.static.snap.net.nz [123.255.30.89]) by viper.snap.net.nz (Postfix) with ESMTP id 2CBC23DA812; Tue, 18 Mar 2008 12:40:52 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id CE3218FC6D; Tue, 18 Mar 2008 11:40:49 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18399.384.473764.852530@kahikatea.snap.net.nz> Date: Mon, 17 Mar 2008 23:41:00 -0000 To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: linux native async mode support In-Reply-To: <200803150157.47855.pedro@codesourcery.com> References: <200803140810.22883.pedro@codesourcery.com> <18395.1471.637574.722785@kahikatea.snap.net.nz> <200803150157.47855.pedro@codesourcery.com> X-Mailer: VM 7.19 under Emacs 23.0.60.42 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00250.txt.bz2 > > Daniel talks about async mode being the default but I don't really > > understand this. In order for Gdb to be able to accept input while the > > inferior is running and possibly accepting it's own input, seems to require > > separate terminals. This isn't a problem for a front end but, in general, > > will be when Gdb is run from the command line. > > This is a confusion of terms. The async mode he was refering to, is > the event loop code path, in which we (ideally) never block in > wait_for_inferior. Maybe it will be useful in non-stop mode but it seems to me that there will always be a problem when the inferior tries to read from/write to the terminal. In any case, async mode is immediately useful for a frontend so, to begin with, it might be a good idea to turn it on by default just for MI. -- Nick http://www.inet.net.nz/~nickrob