Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: Re: Memory Management on AMD64 in 32-bit mode
Date: Sun, 18 Jan 2004 16:58:15 -0500
Message-ID: <E8CC5F35918C084F8DBF32A5161C4003066CF4@mailserver.basistech.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Benson Margulies" <bim2003 AT basistech DOT com>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i0ILwfrh003794

I've belatedly located Corinna Vinschen's email message about the
requirement for the stack address in fork. 

Would anyone be willing to elaborate on how the existing code is going
about accomplishing the task at hand? If not, at least knowing that this
is the goal of the exercise should make it easier to get a clue.

--
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/