From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24158 invoked by alias); 14 Oct 2004 19:01:55 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24126 invoked from network); 14 Oct 2004 19:01:53 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 14 Oct 2004 19:01:53 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i9EJ1rbJ019057 for ; Thu, 14 Oct 2004 15:01:53 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i9EJ1ir23316; Thu, 14 Oct 2004 15:01:53 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D308C28CF; Thu, 14 Oct 2004 15:01:39 -0400 (EDT) Message-ID: <416ECD13.8010001@gnu.org> Date: Fri, 15 Oct 2004 02:36:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20041009 MIME-Version: 1.0 To: Fabian Cenedese Cc: gdb@sources.redhat.com Subject: Re: MI thread commands References: <5.2.0.9.1.20041014090451.01d2d250@NT_SERVER> In-Reply-To: <5.2.0.9.1.20041014090451.01d2d250@NT_SERVER> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00318.txt.bz2 > Hi > > I didn't get a reply on this one so I thought I try again. > > >>>What was the intention behind -thread-info? It's not explained in the >>>manual and also not implemented (so much to "Read the source, Luke"). >>>Should this bring the info that is available with "info threads" but for only >>>one thread? Is there another possibility to get e.g. the thread name? >>> >>>I made my try with the -thread-list-all-threads command, but I'm not >>>sure about the output format as it's nowhere described (Hey Bob, thanks >>>for your rules :) Is this sensible? Or is it one level too much (the >>>"threads=" level)? >>> >>>^done,threads=[thread={id="12",pid="945832",extra=" Name: UserTaskName, State: 0 >>>002, Priority: 0007",frame={func="CTaskTemplateClass::Action",args=[{name="this" >>>,value="0xe6ea8"}],file="N:/Temp/ToThrow/psoism/applicat/src/CTaskTemplateClass. >>>cpp",line="454"}},thread={id="11",pid="956152",extra=" Name: IMP_MAS, State: 000 >>>9, Priority: 0000",frame={func="CINOSTask::MainLoop",args=[{name="this",value="0 >>>xe96f8"}],file="N:/Temp/ToThrow/psoism/os/inos/Src/Inos.cpp",line="856"}}..(snipped)..] > > > Another problem I have is the active thread. If the info thread command is issued > on the CLI gdb will indicate the selected thread with a '*' in front of it. Obviously > that's not possible with the mi. How can this information be returned? Is there > a way to add it to the -thread-list-all-threads, e.g. with a new field "active" only > present in the active thread? Or should it be omitted in this command and put > into a new/other mi command? e.g. the above mentioned -thread-info? Does a GUI, where all threads are displayed equal, have an "active" thread? I guess you're looking to identify the thread at the head of the list of threads that had a reason to stop - breakpoint, signal, ... If MI clients think it's useful, it can be added. Andrew