From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail144.messagelabs.com (mail144.messagelabs.com [216.82.254.51]) by kanga.kvack.org (Postfix) with ESMTP id 4D6DB6B0055 for ; Tue, 16 Jun 2009 15:53:29 -0400 (EDT) Subject: Re: [RFC] set the thread name From: Stefani Seibold In-Reply-To: <36ca99e90906161214u6624014q3f3dc4e234bdf772@mail.gmail.com> References: <1245177592.14543.1.camel@wall-e> <36ca99e90906161214u6624014q3f3dc4e234bdf772@mail.gmail.com> Content-Type: text/plain Date: Tue, 16 Jun 2009 21:54:51 +0200 Message-Id: <1245182091.16466.9.camel@wall-e> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Bert Wesarg Cc: linux-kernel , linux-mm , Andrew Morton List-ID: Am Dienstag, den 16.06.2009, 21:14 +0200 schrieb Bert Wesarg: > Hi, > > On Tue, Jun 16, 2009 at 20:39, Stefani Seibold wrote: > > Currently it is not easy to identify a thread in linux, because there is > > no thread name like in some other OS. > > > > If there were are thread name then we could extend a kernel segv message > > and the /proc//task//... entries by a TName value like this: > prctl(PR_SET_NAME, ...) works perfectly here. > I checked it now a little bit more. It is true it works, but if i do a segv access inside a thread a get the kernel message like: task 09[17395]: segfault at 0 ip 08048612 sp b363c370 error 6 in a.out[8048000+1000] So the current implementation is not exactly what i expect. I would prefer my solution to replace every access thread_struct->comm to task_struct->group_leader->comm to have the right behavior. The new system call is obsolete, it is still there. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org