From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14161 invoked by alias); 19 Jun 2008 03:58:20 -0000 Received: (qmail 14152 invoked by uid 22791); 19 Jun 2008 03:58:19 -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; Thu, 19 Jun 2008 03:58:02 +0000 Received: (qmail 7877 invoked from network); 19 Jun 2008 03:58:00 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 19 Jun 2008 03:58:00 -0000 From: Pedro Alves To: Nick Roberts Subject: Re: [non-stop] 00/10 non-stop mode Date: Thu, 19 Jun 2008 05:07:00 -0000 User-Agent: KMail/1.9.9 Cc: gdb-patches@sourceware.org References: <200806152357.52177.pedro@codesourcery.com> <200806182208.35175.pedro@codesourcery.com> <18521.35420.126987.238633@kahikatea.snap.net.nz> In-Reply-To: <18521.35420.126987.238633@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: <200806190457.59551.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/msg00345.txt.bz2 A Wednesday 18 June 2008 23:21:16, Nick Roberts wrote: > > > 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. > > I mean, for consistency, shouldn't it be: > > maint set non-stop 1 > Ah, I see where you're confused. Enabling async support or not, is something that ideally we shouldn't need to give the user an option for. Therefore, it's a maintainer command, that we'll use until the reasons we have it go away. Selecting non-stop or all-stop modes, is something the user will want to do (even if all-stop mode gets to be implemented on top of non-stop in the future), as both modes are useful. > since this option presumably also only works for linux (and remote?). Just linux currently. remote's in the queue. -- Pedro Alves