Mail Archives: cygwin/2003/04/03/16:50:17
On Thu, Apr 03, 2003 at 11:47:39PM +0200, Corinna Vinschen wrote:
>On Thu, Apr 03, 2003 at 04:37:26PM -0500, Christopher Faylor wrote:
>> I think the only problem is that Cygwin probably just needs to be debugged
>> to see what's going on. If someone wants to send me a nice 64 bit system
>> running WinXP 64 (or whatever it's called), I'll see what I can do.
>
>Coincidentally I was going to suggest something similar...
>
>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.
cgf
--
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/
- Raw text -