From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 109843 invoked by alias); 1 Nov 2019 14:51:26 -0000 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 Received: (qmail 109834 invoked by uid 89); 1 Nov 2019 14:51:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-8.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=nonstop, non-stop X-HELO: gateway32.websitewelcome.com Received: from gateway32.websitewelcome.com (HELO gateway32.websitewelcome.com) (192.185.145.123) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Nov 2019 14:51:25 +0000 Received: from cm11.websitewelcome.com (cm11.websitewelcome.com [100.42.49.5]) by gateway32.websitewelcome.com (Postfix) with ESMTP id 0E6B01E0BFB9 for ; Fri, 1 Nov 2019 09:51:24 -0500 (CDT) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id QYGqi5rYoVUVYQYGqigd57; Fri, 01 Nov 2019 09:51:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=XK7LPZfrYz0j0iaR2rfSuSlccvHbdMV3nV1g1h3y2/g=; b=pN3T+XPFTlKiqD9+sSz4nV98Bf 62HdsgjcPL547o0yc3bH4zGh4temxjUiYoM/3WgmacJ9UtrnRzI+yGsbVFp5KJq7gpacaMBAsV8rx BBcPBSL7b8ET9Q/TFONCsAxHF; Received: from 75-166-66-104.hlrn.qwest.net ([75.166.66.104]:56372 helo=murgatroyd) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1iQYGp-003BgX-P2; Fri, 01 Nov 2019 08:51:23 -0600 From: Tom Tromey To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [PATCH v2 23/24] Require always-non-stop for multi-target resumptions References: <20191017225026.30496-1-palves@redhat.com> <20191017225026.30496-24-palves@redhat.com> Date: Fri, 01 Nov 2019 14:51:00 -0000 In-Reply-To: <20191017225026.30496-24-palves@redhat.com> (Pedro Alves's message of "Thu, 17 Oct 2019 23:50:25 +0100") Message-ID: <877e4j4plh.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2019-11/txt/msg00025.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: Pedro> Currently, we can only support resuming multiple targets at the same Pedro> time if all targets are in non-stop mode (or user-visible all-stop Pedro> mode with target backend in non-stop mode). I don't understand this, but I would like to. I would have thought that target-async would be enough here. As in, the necessary part is that target events be integrated with the event loop, so that multiple event sources can be selected on at once. Why is non-stop needed instead? Tom