Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 13:02:30 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: problem with getppid() Message-ID: <20050915170229.GE26386@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050915153358 DOT GW5555 AT calimero DOT vinschen DOT de> <20050915162909 DOT GA26386 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Thu, Sep 15, 2005 at 09:54:01AM -0700, Eduardo Chappa wrote: >*** Christopher Faylor (pcgf-no-personal-reply-please AT cygwin DOT cometh) wrote...: > >:) If your program looked like this: >:) [removed some sample code, etc] >:) >:) The above is just a suggestion and is not a 100% accurate >:) representation of what needs to be done, of course. > >Right, if this was just my case I could do this (not nice, but could do >it). In my case I need to modify the source code every time I build it, >and since it is a modification to work around a problem in cygwin, I was >hoping that cygwin could be modified so that it would do the right thing, >as it normally does. Btw, if you don't actually care about the ppid value being a real pid, you could add something like this to the list of gdb commands: (gdb) command 1 End with a line saying just "end" set var ppid = 1234 continue end so that ppid would be set automatically. cgf -- 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/