From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28054 invoked by alias); 1 Jul 2015 18:54:40 -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 28042 invoked by uid 89); 1 Jul 2015 18:54:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 01 Jul 2015 18:54:39 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id D6087B8915; Wed, 1 Jul 2015 18:54:37 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t61IsaLP029663; Wed, 1 Jul 2015 14:54:37 -0400 Message-ID: <5594376C.3060907@redhat.com> Date: Wed, 01 Jul 2015 18:54:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Yao Qi , gdb-patches@sourceware.org Subject: Re: [PATCH 00/11] Aarch64 linux GDB native multi-arch debugging (part 1) References: <1435759111-22856-1-git-send-email-yao.qi@linaro.org> <55941CA2.90709@redhat.com> In-Reply-To: <55941CA2.90709@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-07/txt/msg00059.txt.bz2 On 07/01/2015 06:00 PM, Pedro Alves wrote: >> > Patch #9 - #11 can be regarded as an RFC, which teaches GDB to use >> > hardware single step in software single step architecture if target >> > supports hardware single step. They are useful to aarch64 multi-arch >> > debugging, because hardware single step is available for arm32 process >> > on aarch64. > These I think are problematic as is. I didn't say it out loud, but I think the natural solution would be to replace vCont? with new qSupported features. Thanks, Pedro Alves