From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6646 invoked by alias); 11 May 2010 09:23:12 -0000 Received: (qmail 6625 invoked by uid 48); 11 May 2010 09:23:12 -0000 Date: Tue, 11 May 2010 09:23:00 -0000 Message-ID: <20100511092312.6624.qmail@sourceware.org> From: "mjw at redhat dot com" To: gdb-prs@sourceware.org In-Reply-To: <20040114185800.8618.alain@qnx.com> References: <20040114185800.8618.alain@qnx.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug mi/8618] Extract the thread name X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2010-q2/txt/msg00237.txt.bz2 ------- Additional Comments From mjw at redhat dot com 2010-05-11 09:23 ------- This idea was also mentioned here: http://0pointer.de/blog/projects/name-your-threads.html "So, now go, if you have a project which involves a lot of threads, name them all individually, and make it easier to debug them. What's missing now, of course, is that gdb learns this and shows the comm name when doing info threads." -- What |Removed |Added ---------------------------------------------------------------------------- CC| |mjw at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=8618 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.