From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 42927 invoked by alias); 25 Jun 2015 09:28:25 -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 42913 invoked by uid 89); 25 Jun 2015 09:28:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,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, 25 Jun 2015 09:28:14 +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 085D0365073; Thu, 25 Jun 2015 09:28:13 +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 t5P9SAJr031265; Thu, 25 Jun 2015 05:28:12 -0400 Message-ID: <558BC9A9.7000505@redhat.com> Date: Thu, 25 Jun 2015 09:28:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Paul_Koning@Dell.com, gdb@sourceware.org Subject: Re: Thread name in remote stub protocol References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2015-06/txt/msg00084.txt.bz2 On 06/24/2015 09:00 PM, Paul_Koning@Dell.com wrote: > I’ve been looking into FreeBSD threads support, and gdbserver support. FreeBSD has the notion of thread names, and it’s easy enough to make native GDB handle that. gdbserver is another matter. I looked all over the various thread related messages, and while there are a bunch of opportunities for this to be handled, it isn’t really there. > > I can see the deprecated qP packet that carries a “shortname”. That looks interesting, but while the packet parsing is there, it isn’t clear the value goes anywhere. Similarly, there is qThreadExtraInfo which allows for a free form string. And there is qXfer:threads, but that carries only an ID and a core number. And none of these seem to be cleanly tied to the main gdb thread name machinery. > > What to do about this? Could qXfer:threads be extended to add a thread name field? Or should I just use the ThreadExtraInfo mechanism and ignore the fact that it conveys extra info rather than the thread name? https://sourceware.org/ml/gdb-patches/2015-05/msg00370.html Thanks, Pedro Alves