This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: cygwin1.dll (v1.1.2): dup2() with invalid newfd lead to exception: STATUS_ACCESS_VIOLATION
- To: cygwin at sourceware dot cygnus dot com
- Subject: Re: cygwin1.dll (v1.1.2): dup2() with invalid newfd lead to exception: STATUS_ACCESS_VIOLATION
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Mon, 26 Jun 2000 20:59:21 -0400
- References: <8600BF007197944F8DD3906E40CB4280486A@itdomain001.itdomain.net.au>
- Reply-To: cygwin at sourceware dot cygnus dot com
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