From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30347 invoked by alias); 18 May 2009 23:23:25 -0000 Received: (qmail 30338 invoked by uid 22791); 18 May 2009 23:23:24 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 May 2009 23:23:20 +0000 Received: from wpaz29.hot.corp.google.com (wpaz29.hot.corp.google.com [172.24.198.93]) by smtp-out.google.com with ESMTP id n4INNGOS011817 for ; Mon, 18 May 2009 16:23:17 -0700 Received: from wf-out-1314.google.com (wfa28.prod.google.com [10.142.1.28]) by wpaz29.hot.corp.google.com with ESMTP id n4INNF4C026993 for ; Mon, 18 May 2009 16:23:15 -0700 Received: by wf-out-1314.google.com with SMTP id 28so1850232wfa.13 for ; Mon, 18 May 2009 16:23:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.79.17 with SMTP id c17mr2079254wfb.259.1242688995064; Mon, 18 May 2009 16:23:15 -0700 (PDT) In-Reply-To: References: <20090404184604.8524C1C759C@localhost> <200904041904.n34J4UXV013513@brahms.sibelius.xs4all.nl> <20090404192132.GA28232@caradoc.them.org> <20090406033300.GA31715@caradoc.them.org> Date: Mon, 18 May 2009 23:23:00 -0000 Message-ID: Subject: Re: [RFA] improved thread id reporting From: Doug Evans To: gdb-patches Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-05/txt/msg00382.txt.bz2 Ping. Ok to check in? On Thu, May 7, 2009 at 10:46 PM, Doug Evans wrote: > Blech. =A0Right list this time. > > > On Sun, Apr 5, 2009 at 8:33 PM, Daniel Jacobowitz wrote: >> 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? =A0On 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)] > > "works for me" > >> 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. > > It's not clear how multi-process is going to work yet (or more likely > I've forgotten). =A0I played with attaching and running several > processes via gdbserver and all processes appear in "info threads". > [sidebar: I wouldn't mind "info threads" just showing the threads of > the current process, otherwise it might get confusing. =A0And given that > "info inferiors" is used to show all the processes IWBN if "inferior > N" switched to the specified process; a straightforward and intuitive > mapping from "info threads" + "thread N".] > > How about this? >