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/
