From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50482 invoked by alias); 26 Mar 2017 14:02:49 -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 50450 invoked by uid 89); 26 Mar 2017 14:02:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=evil, H*Ad:U*pmuldoon, H*F:D*pl X-HELO: smtpo56.poczta.onet.pl Received: from smtpo56.poczta.onet.pl (HELO smtpo56.poczta.onet.pl) (213.180.142.187) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 26 Mar 2017 14:02:46 +0000 Received: from [192.168.2.253] (83-238-226-97.adsl.inetia.pl [83.238.226.97]) (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 3vrf4H3fmCz18VRL5; Sun, 26 Mar 2017 16:02:38 +0200 (CEST) Message-ID: <1490536958.1290.6.camel@op.pl> Subject: Re: [OpenOCD-devel] Python API for supplying thread information? From: Freddie Chopin To: Steven Stallion Cc: Yao Qi , gdb@sourceware.org, Phil Muldoon , OpenOCD ML Date: Sun, 26 Mar 2017 14:02:00 -0000 In-Reply-To: References: <1490175792.1242.7.camel@op.pl> <4b310e40-3f39-feed-6134-d2cfe68c4423@redhat.com> <1490199596.1410.3.camel@op.pl> <86mvccuszh.fsf@gmail.com> <1490287249.1231.3.camel@op.pl> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00060.txt.bz2 On Thu, 2017-03-23 at 11:46 -0500, Steven Stallion wrote: > There's a bit more to it than that, but that's what users see most > often. It's important to point out that GDB's remote target support > isn't the best; it's not on par with a local target by any means. It > wasn't until recently that thread names could be assigned/sign for > remote targets (7.11.2 IIRC). To the OP, if you're interested in > extending behavior, I'd suggest starting with a small PoC. I think > you'll get a better idea of the issues at hand once you start > exploring the GDB source. This would be a problem, as I'm not really a good desktop programmer (I'm working with microcontrollers only), I also know almost nothing about GDB interals. That's why I was hoping that something like that is actually possible now (directly in GDB or maybe with some evil trickery)... Regards, FCh