From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33540 invoked by alias); 7 Feb 2019 14:22:30 -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 33522 invoked by uid 89); 7 Feb 2019 14:22:30 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-26.9 required=5.0 tests=BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=maintains X-HELO: gateway33.websitewelcome.com Received: from gateway33.websitewelcome.com (HELO gateway33.websitewelcome.com) (192.185.146.195) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 07 Feb 2019 14:22:28 +0000 Received: from cm14.websitewelcome.com (cm14.websitewelcome.com [100.42.49.7]) by gateway33.websitewelcome.com (Postfix) with ESMTP id 1694542B1079 for ; Thu, 7 Feb 2019 03:40:26 -0600 (CST) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id rgAUgooQB2qH7rgAUgNzHO; Thu, 07 Feb 2019 03:40:26 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=References:In-Reply-To:Message-Id:Date:Subject:Cc:To:From: Sender:Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=iAyRGFArPYhWToxA6Z1I2wOZvZb56XGk6EsR+OsPH3w=; b=AUg9N9CMjrvq5aO02JPYP+kZ/R GnPrWb1HQwZsu0zZSOzLBlKBXPnh6kmlJ4xwjO/P55S7nmzSWKGiRg4JfJi3KipwNhPWegSGA5C7M CgjRAgjFfY7Inz5duMiVcir8x; Received: from dhcp-guest.act-europe.fr ([194.98.77.127]:61727 helo=bapiya.act-europe.fr) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1grgAT-003W3S-I6; Thu, 07 Feb 2019 03:40:25 -0600 From: Tom Tromey To: gdb-patches@sourceware.org Cc: Tom Tromey Subject: [PATCH 1/8] Fix some typos in ravenscar-thread.c Date: Thu, 07 Feb 2019 14:22:00 -0000 Message-Id: <20190207094016.368-2-tom@tromey.com> In-Reply-To: <20190207094016.368-1-tom@tromey.com> References: <20190207094016.368-1-tom@tromey.com> X-SW-Source: 2019-02/txt/msg00063.txt.bz2 From: Tom Tromey This fixes some typos I noticed in ravenscar-thread.c. gdb/ChangeLog 2019-02-07 Tom Tromey * ravenscar-thread.c: Fix some typos. --- gdb/ChangeLog | 4 ++++ gdb/ravenscar-thread.c | 10 +++++----- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/gdb/ravenscar-thread.c b/gdb/ravenscar-thread.c index bc7f9d6c658..32a4aa8d16a 100644 --- a/gdb/ravenscar-thread.c +++ b/gdb/ravenscar-thread.c @@ -36,7 +36,7 @@ The typical situation is when debugging a bare-metal target over the remote protocol. In that situation, the system does not know - about high-level comcepts such as threads, only about some code + about high-level concepts such as threads, only about some code running on one or more CPUs. And since the remote protocol does not provide any handling for CPUs, the de facto standard for handling them is to have one thread per CPU, where the thread's ptid has @@ -44,14 +44,14 @@ 2 for the second one, etc). This module will make that assumption. This module then creates and maintains the list of threads based - on the list of Ada tasks, with one thread per Ada tasks. The convention + on the list of Ada tasks, with one thread per Ada task. The convention is that threads corresponding to the CPUs (see assumption above) - have a ptid_t of the form (PID, LWP, 0), which threads corresponding + have a ptid_t of the form (PID, LWP, 0), while threads corresponding to our Ada tasks have a ptid_t of the form (PID, 0, TID) where TID is the Ada task's ID as extracted from Ada runtime information. - Switching to a given Ada tasks (or its underlying thread) is performed - by fetching the registers of that tasks from the memory area where + Switching to a given Ada task (or its underlying thread) is performed + by fetching the registers of that task from the memory area where the registers were saved. For any of the other operations, the operation is performed by first finding the CPU on which the task is running, switching to its corresponding ptid, and then performing -- 2.17.2