From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1282 invoked by alias); 6 Oct 2005 12:34:27 -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 1249 invoked by uid 22791); 6 Oct 2005 12:34:24 -0000 Received: from qnxmail.qnx.com (HELO nimbus.ott.qnx.com) (209.226.137.76) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 06 Oct 2005 12:34:24 +0000 Received: by nimbus.ott.qnx.com with Internet Mail Service (5.5.2653.19) id ; Thu, 6 Oct 2005 08:34:20 -0400 Message-ID: <3518719F06577C4F85DA618E3C37AB9101CFC7E0@nimbus.ott.qnx.com> From: Kris Warkentin To: 'Daniel Jacobowitz' , Kris Warkentin Cc: GDB Subject: RE: [RFC] named thread support Date: Thu, 06 Oct 2005 12:34:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2005-10/txt/msg00028.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? Exactly. When I implemented the reading of the names from the target it occurred to me that I could set names as well. It's not a super useful or high priority item but it's easy and fun so I thought I'd do it anyway. ;-) > I recommend doing this in your backend, since I don't know any other > gdb-supported system with a similar feature. No problem. cheers, Kris