From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18300 invoked by alias); 6 Apr 2009 03:33:09 -0000 Received: (qmail 18292 invoked by uid 22791); 6 Apr 2009 03:33:08 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 06 Apr 2009 03:33:03 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 23FFC7C09B for ; Mon, 6 Apr 2009 03:33:02 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id EB7397C09A for ; Mon, 6 Apr 2009 03:33:01 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Lqfa0-0008Ka-Rn for gdb@sourceware.org; Sun, 05 Apr 2009 23:33:00 -0400 Date: Mon, 06 Apr 2009 07:39:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: improved thread id reporting Message-ID: <20090406033300.GA31715@caradoc.them.org> Mail-Followup-To: gdb@sourceware.org References: <20090404184604.8524C1C759C@localhost> <200904041904.n34J4UXV013513@brahms.sibelius.xs4all.nl> <20090404192132.GA28232@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00069.txt.bz2 On Sun, Apr 05, 2009 at 01:36:06PM -0700, Doug Evans wrote: > Attached is a simplistic patch to help illustrate the challenge. > > Here is an example session that prints from/to and the thread number > in "[New ...", "[Switching ...", etc. messages. > I can think of two issues with the patch: > 1) Printing "[tT]hread" twice in one line is a bit annoying. > 2) Spreading from/to over two lines is a bit annoying. What do you think of this? On the theory that you can go look up thread #2, either in 'info threads' or in a previous notification: [Switching from thread #2 to thread #3, Thread 0x41001960 (LWP 14407)] Or, migrating the "Thread" out: [Switching from thread #2 to thread #3, 0x41001960 (LWP 14407)] But that might be tricky with multi-process, some ptid_t's are not threads. -- Daniel Jacobowitz CodeSourcery