From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-30302-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 9803 invoked by alias); 22 Nov 2007 00:23:22 -0000
Received: (qmail 9792 invoked by uid 22791); 22 Nov 2007 00:23:21 -0000
X-Spam-Check-By: sourceware.org
Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 22 Nov 2007 00:23:16 +0000
Received: from zps36.corp.google.com (zps36.corp.google.com [172.25.146.36]) 	by smtp-out.google.com with ESMTP id lAM0N8HQ011817 	for <gdb@sourceware.org>; Thu, 22 Nov 2007 00:23:11 GMT
Received: from ug-out-1314.google.com (ugfc2.prod.google.com [10.66.180.2]) 	by zps36.corp.google.com with ESMTP id lAM0N7WV023506 	for <gdb@sourceware.org>; Wed, 21 Nov 2007 16:23:07 -0800
Received: by ug-out-1314.google.com with SMTP id c2so226973ugf         for <gdb@sourceware.org>; Wed, 21 Nov 2007 16:23:06 -0800 (PST)
Received: by 10.66.220.17 with SMTP id s17mr258169ugg.1195690986711;         Wed, 21 Nov 2007 16:23:06 -0800 (PST)
Received: by 10.67.21.14 with HTTP; Wed, 21 Nov 2007 16:23:06 -0800 (PST)
Message-ID: <e394668d0711211623v672e5f75seb72752a7456f000@mail.gmail.com>
Date: Thu, 22 Nov 2007 00:23:00 -0000
From: "Douglas Evans" <dje@google.com>
To: gdb@sourceware.org
Subject: inconsistency in thread naming
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-IsSubscribed: yes
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: 2007-11/txt/msg00214.txt.bz2

When gdb switches to a particular thread it prints something like

[Switching to Thread 12345]

But the "thread" command takes thread numbers, e.g.

(gdb) thread 3

This inconsistency is a pain.  Any objections to making things more
consistent?  Any opinions on how this should work?  A minimalist
solution might be to include the thread number (3 in the above
example) in the [Switching to ...] message.  If there was a consistent
way to distinguish thread number(3) from thread id(12345) [apologies
if my terminology if wrong], then the "thread" command could take
either.  E.g. one might support "thread 3" or "thread #12345".  I
don't have a strong opinion on what to choose, I'm just thinking out
loud.