Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Thu, 15 Sep 2005 17:33:58 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: problem with getppid()
Message-ID:	<20050915153358.GW5555@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<Pine DOT LNX DOT 4 DOT 63 DOT 0509150809440 DOT 23407 AT zeno1 DOT math DOT washington DOT edu>
Mime-Version:	1.0
In-Reply-To:	<Pine.LNX.4.63.0509150809440.23407@zeno1.math.washington.edu>
User-Agent:	Mutt/1.4.2i

On Sep 15 08:14, Eduardo Chappa wrote:
> gdb ./test
> (gdb) run
> 
> The output is "My parent is bad". I believe this is a bug in Cygwin's 
> implementation of getppid().

No, it's not a bug.  GDB starts the inferior process using the standard
Windows mechanisms since it should be useful also for native debugging.
When the inferior process is not started by Cygwin's own fork/exec
process, the child process doesn't know anything about its parent process,
at least not on Windows 9x.  There's a way to retrieve the native parent
PID by using NtQueryInformationProcess on NT, but it doesn't seem very
useful to get this information.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

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

- Raw text -