Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Mon, 26 Jun 2000 20:59:21 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: cygwin1.dll (v1.1.2): dup2() with invalid newfd lead to exception: STATUS_ACCESS_VIOLATION Message-ID: <20000626205921.B10283@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <8600BF007197944F8DD3906E40CB4280486A@itdomain001.itdomain.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <8600BF007197944F8DD3906E40CB4280486A@itdomain001.itdomain.net.au>; from robert.collins@itdomain.com.au on Tue, Jun 27, 2000 at 10:09:34AM +1000 On Tue, Jun 27, 2000 at 10:09:34AM +1000, Robert Collins wrote: >AFAICT the stackdumps occurs in fork() itself. I will try your >suggestion for getting the child process pid though. > >I should have used process not thread before (oops), but nonetheless I >thought gdb had an option when fork() is called to follow the parent or >child process? I tried setting that when debugging but got nowhere. The option is not implemented on very many platforms. Windows is one of the many where it doesn't work. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com