X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 15 Oct 2009 13:33:08 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: fork failure?
Message-ID: <20091015173308.GC12892@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4AD732C7 DOT 4020301 AT cwilson DOT fastmail DOT fm>  <4AD73B83 DOT 9060505 AT gmail DOT com>  <4AD74586 DOT 8070803 AT cwilson DOT fastmail DOT fm>  <4AD752C8 DOT 2040908 AT gmail DOT com>  <4AD756BE DOT 6050204 AT cwilson DOT fastmail DOT fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AD756BE.6050204@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Thu, Oct 15, 2009 at 01:07:10PM -0400, Charles Wilson wrote:
>Dave Korn wrote:
>> Charles Wilson wrote:
>>> the daemonized one.  If I launch <cmd line> and then attach strace to
>>> the eventual pid of the daemonized process, it hangs (both strace and
>>> the process).  
>> 
>>   How about "gdb --attach PID"?  Does that succeed?  GDB has the advantage of
>> being a Cygwin rather than Win32 exe, which might make it work better when
>> taking hold of the running process.
>
>Well, since we don't support set fork-follow-child, I'm stuck in the
>parent (and I don't get far enough in the child to reach a 'sleep(N)'
>call, so the typical attach-after-fork approach won't work either).  And
>the parent thinks everything is fine.  I haven't tried linking against a
>debug-built DLL so as to step into the fork() call itself (hmm...why
>aren't the cygwin1.dbg files available for the 1.7.0-nn releases? They
>used to be shipped with 1.5.2x releases...)

...different person doing the release...

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple