Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Fri, 2 Mar 2001 14:40:59 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Make hung in WaitForMultipleObjects inside Cygwin
Message-ID:	<20010302144059.B16125@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20010228155722 DOT 21696 DOT qmail AT lizard DOT curl DOT com> <20010228162324 DOT 21997 DOT qmail AT lizard DOT curl DOT com> <20010228163528 DOT 22101 DOT qmail AT lizard DOT curl DOT com> <20010301210358 DOT 31563 DOT qmail AT lizard DOT curl DOT com> <20010302185213 DOT 19881 DOT qmail AT lizard DOT curl DOT com> <22288145100 DOT 20010302222958 AT logos-m DOT ru> <20010302193602 DOT 22711 DOT qmail AT lizard DOT curl DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<20010302193602.22711.qmail@lizard.curl.com>; from jik@curl.com on Fri, Mar 02, 2001 at 02:36:02PM -0500

On Fri, Mar 02, 2001 at 02:36:02PM -0500, Jonathan Kamens wrote:
>>  Date: Fri, 2 Mar 2001 22:29:58 +0300
>>  From: Egor Duda <deo AT logos-m DOT ru>
>>  
>>  did  you use win32-style pid when tried to attach to process from gdb?
>
>Yes.  Actually, I tried both just to be safe, but I knew that gdb was
>expecting the Windows PID.
>
>>  gdb  expects  win32-style  pid  (shown  with 'ps -l' command).
>
>Yes, I know.
>
>>  Most of time,  cygwin  pid  is equal to native one,
>
>Really?  I haven't found that to be the case.  For example, of 11
>Cygwin processes currently running on my machine, the Windows PID of
>six of them (i.e., over half) is different from the Cygwin PID.  Are
>we doing something unusual to provoke such behavior?  Is it relevant
>to the problem we're having?

No.  The cygwin pid != windows pid after an exec occurs.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -