From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21049 invoked by alias); 18 Jun 2008 21:08:55 -0000 Received: (qmail 21039 invoked by uid 22791); 18 Jun 2008 21:08:55 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 18 Jun 2008 21:08:37 +0000 Received: (qmail 29204 invoked from network); 18 Jun 2008 21:08:36 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Jun 2008 21:08:36 -0000 From: Pedro Alves To: Nick Roberts Subject: Re: [non-stop] 00/10 non-stop mode Date: Wed, 18 Jun 2008 21:37:00 -0000 User-Agent: KMail/1.9.9 Cc: gdb-patches@sourceware.org References: <200806152357.52177.pedro@codesourcery.com> <200806181440.07812.pedro@codesourcery.com> <18521.29761.674435.357159@kahikatea.snap.net.nz> In-Reply-To: <18521.29761.674435.357159@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806182208.35175.pedro@codesourcery.com> 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-06/txt/msg00338.txt.bz2 A Wednesday 18 June 2008 21:46:57, Nick Roberts wrote: > > > > # Enable the async interface > > > > maint set linux-async 1 > > > > > > Why is this still a maintenance command while the others aren't? > > > > Because, (if you remember, we've talked about this before)there are > > issues with async mode that prevent it from being the default (core > > side, not linux only). > > In that case I'm not really sure what you mean by core - non-stop mode > includes changes to linux-nat.c, so presumably that is linux only. I don't follow where you're getting at. Async mode requires target support, but of course there's also code in the core of GDB to support it. Non-stop mode requires target support, builds on top of the async mode, and of course needs core support too. The async limitations are in the core side, and affect any async target -- currently only linux and remote. We could merge "maint set linux-async" and "maint set remote-async" into one global "maint set async", I don't see a problem with that. -- Pedro Alves