From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19229 invoked by alias); 29 Jul 2013 18:42:12 -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 19216 invoked by uid 89); 29 Jul 2013 18:42:11 -0000 X-Spam-SWARE-Status: No, score=-5.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 29 Jul 2013 18:42:11 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r6TIg2Lm027351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 29 Jul 2013 14:42:02 -0400 Received: from barimba (ovpn-113-128.phx2.redhat.com [10.3.113.128]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r6TIg1HM030111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 29 Jul 2013 14:42:02 -0400 From: Tom Tromey To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [PATCH 8/8] enable target-async References: <1375116324-32092-1-git-send-email-tromey@redhat.com> <1375116324-32092-9-git-send-email-tromey@redhat.com> <83k3k9xlrs.fsf@gnu.org> Date: Mon, 29 Jul 2013 18:42:00 -0000 In-Reply-To: <83k3k9xlrs.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 29 Jul 2013 21:29:27 +0300") Message-ID: <87r4ehnr7q.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-07/txt/msg00731.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Eli> However, I have a question: what does this change mean for targets Eli> that don't support target-async? Do they always get an error message Eli> when GDB starts? I don't think they will. All it will mean is that if the user tries to use the "&" suffix on a command, like "run &", then he will get an error. An MI client will still see an error if it tries to set target-async. This is also no different from today. Tom