From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-34105-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 10067 invoked by alias); 3 Apr 2009 18:15:51 -0000
Received: (qmail 10053 invoked by uid 22791); 3 Apr 2009 18:15:48 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 03 Apr 2009 18:15:33 +0000
Received: (qmail 24866 invoked from network); 3 Apr 2009 18:15:29 -0000
Received: from unknown (HELO orlando.local) (pedro@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 3 Apr 2009 18:15:29 -0000
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Subject: Re: About "process 42000"
Date: Fri, 03 Apr 2009 19:30:00 -0000
User-Agent: KMail/1.9.10
Cc: Michael Snyder <msnyder@vmware.com>,  Shrinand Javadekar <shrinand@gmail.com>
References: <fe51cfa60904021742w99c2a16he506e10a01d1bb67@mail.gmail.com> <fe51cfa60904021810o7eb2c736p7de224dc1d181956@mail.gmail.com> <49D64E5A.6020604@vmware.com>
In-Reply-To: <49D64E5A.6020604@vmware.com>
MIME-Version: 1.0
Content-Type: text/plain;   charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200904031915.47714.pedro@codesourcery.com>
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: 2009-04/txt/msg00039.txt.bz2

On Friday 03 April 2009 18:58:50, Michael Snyder wrote:
> Shrinand Javadekar wrote:
> > Hi,
> > 
> > I see "process 42000" in the output of an "info threads" command.
> > 
> > What exactly is this process with id 42000? And what is its significance?
> 
> In the past, 42000 was a magic thread id that was supplied by remote.c
> in the case where we did not have any actual thread ids.
> 
> Now, however, I am seeing it even in cases where we do have
> a list of real thread ids from the remote target.
> 
> Seems like a bug to me...

Can you be a bit more specific?  A gdb log showing what you're talking
about would be helpful.  A debug remote log would probably also help.
Since there are a bunch of optional packets, I may have
missed some combination.

-- 
Pedro Alves