From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23965 invoked by alias); 15 May 2013 07:40:53 -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 23952 invoked by uid 89); 15 May 2013 07:40:52 -0000 X-Spam-SWARE-Status: No, score=-4.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL autolearn=ham version=3.3.1 Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 15 May 2013 07:40:51 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1UcWKP-0004wH-Pn from Yao_Qi@mentor.com ; Wed, 15 May 2013 00:40:49 -0700 Received: from SVR-ORW-FEM-05.mgc.mentorg.com ([147.34.97.43]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 15 May 2013 00:40:49 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.2.247.3; Wed, 15 May 2013 00:40:48 -0700 Message-ID: <51933C0B.1060109@codesourcery.com> Date: Wed, 15 May 2013 07:40:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pedro Alves CC: Subject: Re: [PATCH 3/7] range stepping: gdbserver on x86/linux References: <1363006291-13334-1-git-send-email-yao@codesourcery.com> <1363006291-13334-4-git-send-email-yao@codesourcery.com> <519282CB.4030800@redhat.com> In-Reply-To: <519282CB.4030800@redhat.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2013-05/txt/msg00506.txt.bz2 On 05/15/2013 02:30 AM, Pedro Alves wrote: > - it assumes GDB will ever only send one r action per vCont. I'd much > rather we don't bake in that assumption. > I am afraid not. It works for multiple r actions in one vCont. > - It seems like this leaves threads with stale step ranges. Because > linux-low.c only clears the stepping range of the thread that is reporting > the event (here): OK. Looks we need to call thread_clear_range_stepping for the thread we parsed in handle_v_cont first. -- Yao (齐尧)