From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 71345 invoked by alias); 2 Jul 2015 08:56: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 71334 invoked by uid 89); 2 Jul 2015 08:56:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-pa0-f48.google.com Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com) (209.85.220.48) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 02 Jul 2015 08:56:25 +0000 Received: by paceq1 with SMTP id eq1so37320193pac.3 for ; Thu, 02 Jul 2015 01:56:23 -0700 (PDT) X-Received: by 10.66.145.33 with SMTP id sr1mr63135179pab.41.1435827383315; Thu, 02 Jul 2015 01:56:23 -0700 (PDT) Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137]) by mx.google.com with ESMTPSA id fm3sm4875884pdb.28.2015.07.02.01.56.21 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 02 Jul 2015 01:56:22 -0700 (PDT) From: Yao Qi To: Pedro Alves Cc: Yao Qi , gdb-patches@sourceware.org Subject: Re: [PATCH 11/11] New target_ops hook to_can_do_single_step References: <1435759111-22856-1-git-send-email-yao.qi@linaro.org> <1435759111-22856-12-git-send-email-yao.qi@linaro.org> <55941892.3000902@redhat.com> Date: Thu, 02 Jul 2015 08:56:00 -0000 In-Reply-To: <55941892.3000902@redhat.com> (Pedro Alves's message of "Wed, 01 Jul 2015 17:42:58 +0100") Message-ID: <866163os3x.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-07/txt/msg00069.txt.bz2 Pedro Alves writes: > But my issue with it is that this breaks gdb/gdbserver compatibility. > > Old GDB has: > > /* If s, S, c, and C are not all supported, we can't use vCont. Cl= earing > BUF will make packet_ok disable the packet. */ > if (!support_s || !support_S || !support_c || !support_C) > buf[0] =3D 0; > > Which means that new x86-86 gdbserver with old gdb will just > stop using vCont after this change. I think you meant new arm gdbserver, which doesn't return s and S in the reply, old gdb will stop using vCont. > > And old arm gdbserver will still claim support for vCont;s packets, > which means that new gdb with old gdbserver will be broken. That is right. I'll do it in qSupported features. --=20 Yao (=E9=BD=90=E5=B0=A7)