From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22231 invoked by alias); 26 Nov 2015 17:56:22 -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 22221 invoked by uid 89); 26 Nov 2015 17:56:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham 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; Thu, 26 Nov 2015 17:56:21 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id 9DF401EB23; Thu, 26 Nov 2015 17:56:20 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tAQHuJbN019770; Thu, 26 Nov 2015 12:56:19 -0500 Message-ID: <565747C2.3010609@redhat.com> Date: Thu, 26 Nov 2015 17:56:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Yao Qi CC: gdb-patches@sourceware.org Subject: Re: [PATCH 11/18] gdbserver: fix killed-outside.exp References: <1444836486-25679-1-git-send-email-palves@redhat.com> <1444836486-25679-12-git-send-email-palves@redhat.com> <86ziz4zlof.fsf@gmail.com> <5655CE81.3090603@redhat.com> <86fuzswvov.fsf@gmail.com> In-Reply-To: <86fuzswvov.fsf@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-11/txt/msg00576.txt.bz2 On 11/26/2015 04:51 PM, Yao Qi wrote: > By the way, after GDBserver reported the stop GDB, does the thread > changed to > > (thread->last_resume_kind == resume_stop > && thread->last_status.kind != TARGET_WAITKIND_IGNORE) > > it is used in proceed_one_lwp. > Yes, after the stop is reported out of linux_wait, server.c does: else { /* We're reporting this thread as stopped. Update its "want-stopped" state to what the client wants, until it gets a new resume action. */ current_thread->last_resume_kind = resume_stop; current_thread->last_status = last_status; } Thanks, Pedro Alves