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, 3 Apr 2003 23:56:53 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Big Brother is Real Message-ID: <20030403215653.GX18138@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030403213726 DOT GC18494 AT redhat DOT com> <20030403214739 DOT GW18138 AT cygbert DOT vinschen DOT de> <20030403214943 DOT GA18771 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030403214943.GA18771@redhat.com> User-Agent: Mutt/1.4.1i On Thu, Apr 03, 2003 at 04:49:43PM -0500, Christopher Faylor wrote: > On Thu, Apr 03, 2003 at 11:47:39PM +0200, Corinna Vinschen wrote: > >I got a hint lately about stuff working different on 64bit. If a 32 bit > >application is called from a 64 bit application the stack is 0xc000 > >lower than if the same 32 bit application is called by another 32 bit > >application. E. g., the first bash is spawned from 64 bit cmd.exe, its > >stack is shifted 0xc000. A CreateProcess call from fork will now create > >a child with the stack at another location which breaks the longjmp. > > That shouldn't be a problem. That's no different than if fork() is > called from another thread. The stack should be relocated in the forkee > automatically unless the memory for the stack is being used for something > else. Hmm, this was apparently the reason it didn't work. The guy tracked it down to the longjmp which SEGV'd since it tried to return to an invalid memory region. But anyway, fork is your child. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/