From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8427 invoked by alias); 18 Jan 2016 17:13:40 -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 8400 invoked by uid 89); 18 Jan 2016 17:13:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=to_thread_name X-Spam-User: qpsmtpd, 2 recipients 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; Mon, 18 Jan 2016 17:13:39 +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 11A608E01B; Mon, 18 Jan 2016 17:13:38 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u0IHDaDF025524; Mon, 18 Jan 2016 12:13:37 -0500 Message-ID: <569D1D40.6070809@redhat.com> Date: Mon, 18 Jan 2016 17:13: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: John Baldwin CC: gdb-patches@sourceware.org, binutils@sourceware.org Subject: Re: [PATCH v2 3/6] Display per-thread information for threads in FreeBSD cores. References: <1452721551-657-1-git-send-email-jhb@FreeBSD.org> <2320320.x23qbZCVbY@ralph.baldwin.cx> <569CDA29.3050000@redhat.com> <1701896.llh381Sx0a@ralph.baldwin.cx> In-Reply-To: <1701896.llh381Sx0a@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-01/txt/msg00392.txt.bz2 On 01/18/2016 05:05 PM, John Baldwin wrote: > Alternatively, would it be best if the core target defined a to_thread_name > method that invoked a new gdbarch method (gdbarch_core_thread_name or the > like) to fetch the thread name? Yes, that's the right way to go. Thanks, Pedro Alves