From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4509 invoked by alias); 6 Oct 2005 01:21:43 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4476 invoked by uid 22791); 6 Oct 2005 01:21:41 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 06 Oct 2005 01:21:41 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1ENKS3-0005Xj-Mi; Wed, 05 Oct 2005 21:21:39 -0400 Date: Thu, 06 Oct 2005 01:21:00 -0000 From: Daniel Jacobowitz To: Kris Warkentin Cc: GDB Subject: Re: [RFC] named thread support Message-ID: <20051006012139.GA21277@nevyn.them.org> Mail-Followup-To: Kris Warkentin , GDB References: <4342B076.3000709@qnx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4342B076.3000709@qnx.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-10/txt/msg00024.txt.bz2 On Tue, Oct 04, 2005 at 12:40:22PM -0400, Kris Warkentin wrote: > Would it be of interest to have a generic 'set threadname ' > that called a target_set_threadname()? I ask because we're implementing > named threads in our kernel but I don't know if many other systems > support this. I can always add it to our backend but if someone else > might use it in the future, I can make it general. So by named thread support, you mean that the application can register the name of the thread with the kernel? And you want GDB to be able to set thread names? I recommend doing this in your backend, since I don't know any other gdb-supported system with a similar feature. -- Daniel Jacobowitz CodeSourcery, LLC