From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13278 invoked by alias); 19 Sep 2006 21:03:23 -0000 Received: (qmail 13270 invoked by uid 22791); 19 Sep 2006 21:03:22 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 19 Sep 2006 21:03:20 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GPmkO-0004Zf-6k; Tue, 19 Sep 2006 17:03:16 -0400 Date: Tue, 19 Sep 2006 21:03:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Denis PILAT , gdb@sourceware.org Subject: Re: info thread Message-ID: <20060919210316.GA17479@nevyn.them.org> Mail-Followup-To: Nick Roberts , Denis PILAT , gdb@sourceware.org References: <17679.5055.729126.253019@kahikatea.snap.net.nz> <450FED7C.1050902@st.com> <17680.22719.512121.415472@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17680.22719.512121.415472@kahikatea.snap.net.nz> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00115.txt.bz2 On Wed, Sep 20, 2006 at 08:53:19AM +1200, Nick Roberts wrote: > There is no specification so we can only guess what was intended. Perhaps > -thread-info was just meant to give info for the selected thread which > presumably would not take long to compute even with all the details. In any > case, as Daniel says, the problem is to devise one(s) which is/are generally > useful. > > I would guess the reason that they haven't already been implemented is that > the other information is kernel/OS dependent e.g on GNU/Linux I get: This isn't really relevant. It breaks down into just a few parts in GDB parlance: - The GDB ID. That's "1", "2", et cetera in your example. - The thread ID, produced by to_pid_to_str, e.g. "Thread -BLAH (LWP BLAH)". This is just a string. - The thread extra info. Not present in your example, but e.g. "(Exiting)" or "(not ready)". - The thread's current stack frame. That last, I think, is not useful in MI. There's commands to fetch it when it's wanted, and it might not be by some consumers. And it will show up with -thread-select already. So, I would recommend including only the GDB ID (as from -thread-list-ids) and the additional information. Whether they should be one field or two is anybody's guess. -- Daniel Jacobowitz CodeSourcery