Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Sun, 26 May 2002 21:50:27 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Problem in strace -p pid
Message-ID: <20020527015027.GC15710@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <023901c2051c$92846ad0$6132bc3e AT BABEL>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <023901c2051c$92846ad0$6132bc3e@BABEL>
User-Agent: Mutt/1.3.23.1i

On Mon, May 27, 2002 at 02:19:39AM +0100, Conrad Scott wrote:
>There is unfortunately a race, since (on w2k at least) the target process is
>not being debugged by the time it receives the magic __SIGSTRACE signal.

I'm not sure that I understand how this type of race is possible.  It seems
like once DebugActiveProcess returns the process in question should consider
itself to be debugged.  However, this wouldn't be the first time that I've
been surprised by Microsoft.

However, I've checked in a fix which should work around your reported
problem.

Thanks for the detailed analysis.

cgf