From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27434 invoked by alias); 3 Apr 2009 21:46:35 -0000 Received: (qmail 27422 invoked by uid 22791); 3 Apr 2009 21:46:34 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from rv-out-0708.google.com (HELO rv-out-0708.google.com) (209.85.198.249) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 03 Apr 2009 21:46:28 +0000 Received: by rv-out-0708.google.com with SMTP id l33so1138050rvb.48 for ; Fri, 03 Apr 2009 14:46:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.134.10 with SMTP id h10mr725227rvd.287.1238795185651; Fri, 03 Apr 2009 14:46:25 -0700 (PDT) In-Reply-To: <200904031915.47714.pedro@codesourcery.com> References: <49D64E5A.6020604@vmware.com> <200904031915.47714.pedro@codesourcery.com> Date: Fri, 03 Apr 2009 22:00:00 -0000 Message-ID: Subject: Re: About "process 42000" From: Shrinand Javadekar To: Pedro Alves , gdb@sourceware.org, Michael Snyder Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00042.txt.bz2 Ooops... I think this was because of my mistake. I have my own gdb server. In the list of processes being returned for "info threads", I was returning a process with pid 0. Gdb would then give this a process id of 42000. Sending packet: $qsThreadInfo#c8...Ack Packet received: m0 [New process 42000] Gdb then shows "process 42000" in the output. However, from here on, it does not try to find out if this process is alive. It will always show "process 42000" in the output. So every "info threads" command after this one will have "process 42000" in the output. Thank you everyone. -Shri On Fri, Apr 3, 2009 at 11:15 AM, Pedro Alves wrote: > 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 significan= ce? >> >> 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? =C2=A0A gdb log showing what you're talki= ng > about would be helpful. =C2=A0A debug remote log would probably also help. > Since there are a bunch of optional packets, I may have > missed some combination. > > -- > Pedro Alves > --=20 Discover the 'web' of videos www.videonym.com