From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-31989-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 19823 invoked by alias); 5 Jun 2008 05:50:45 -0000
Received: (qmail 19812 invoked by uid 22791); 5 Jun 2008 05:50:44 -0000
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 05 Jun 2008 05:50:26 +0000
Received: (qmail 32399 invoked from network); 5 Jun 2008 05:50:24 -0000
Received: from unknown (HELO localhost) (vladimir@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 5 Jun 2008 05:50:24 -0000
From: Vladimir Prus <vladimir@codesourcery.com>
To: Pawel Piech <pawel.piech@windriver.com>,  gdb@sources.redhat.com
Subject: Re: non-stop and current thread exiting
Date: Thu, 05 Jun 2008 05:50:00 -0000
User-Agent: KMail/1.9.9
References: <200806032253.39575.pedro@codesourcery.com> <g26jua$4ps$1@ger.gmane.org> <4846F753.7060204@windriver.com>
In-Reply-To: <4846F753.7060204@windriver.com>
MIME-Version: 1.0
Content-Type: text/plain;   charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200806050950.19833.vladimir@codesourcery.com>
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-06/txt/msg00026.txt.bz2

On Thursday 05 June 2008 00:13:07 you wrote:
>  As far as I remember -thread-info displays information
>  about a single thread, though I don't think it's implemented.=A0=20
>  -thread-list-all-threads which is supposed to be equivalent to info=20
>  threads, could show exited threads and let the UI filter them out.=A0=20
>  However -thread-list-ids, which is actually implemented, only lists IDs,=
=20
>  so there's no way for the UI to tell which ones are live.=20=20=20=20=20

-thread-info is implemented in CVS HEAD, and can either report all threads
(when used without a parameter), or a specific thread. There's also a patch
to make it report, for each thread, if it's running or not.
-thread-list-all-threads will not be implemented, in light of current
 -thread-info behaviour.
-thread-list-ids is a historical artefact, using it is strictly inferiour
to -thread-info, and the frontend should first probe -thread-info and use
-thread-list-ids as a fallback only.

- Volodya