From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18726 invoked by alias); 22 Mar 2017 11:46:33 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 18713 invoked by uid 89); 22 Mar 2017 11:46:32 -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,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=increasing, popularity, FCh, rtos X-HELO: smtpo27.poczta.onet.pl Received: from smtpo27.poczta.onet.pl (HELO smtpo27.poczta.onet.pl) (213.180.142.158) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 22 Mar 2017 11:46:30 +0000 Received: from [192.168.2.253] (213-238-86-67.adsl.inetia.pl [213.238.86.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: freddie_chopin@op.pl) by smtp.poczta.onet.pl (Onet) with ESMTPSA id 3vp7Dw5nb1zmTT5D; Wed, 22 Mar 2017 12:46:24 +0100 (CET) Message-ID: <1490183183.1242.18.camel@op.pl> Subject: Re: [OpenOCD-devel] Python API for supplying thread information? From: Freddie Chopin To: Liviu Ionescu Cc: gdb@sourceware.org, openocd-devel Date: Wed, 22 Mar 2017 11:46:00 -0000 In-Reply-To: <8FB0BA0B-F013-48A6-965B-AEF4B69610EC@livius.net> References: <1490175792.1242.7.camel@op.pl> <8FB0BA0B-F013-48A6-965B-AEF4B69610EC@livius.net> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00035.txt.bz2 On Wed, 2017-03-22 at 13:01 +0200, Liviu Ionescu wrote: > even if this is possible, it does not cover all debugging tools > (increasing in popularity right now, at least for FreeRTOS) that > might need to introspect the RTOS, for example Eclipse plug-ins to > display the status of semaphores, queues, memory allocators, etc. The tools you mentioned clearly don't use OpenOCD's RTOS support or GDB's thread info for that anyway, as neither provides any info about things you mentioned (semaphores, queues, allocators, ...). So that hypothetical change that I suggested neither prevents nor enables them to do that. And if these tools do that now, they do that by directly accessing target memory via GDB, so no special support for anything like that is required. Regards, FCh