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
Date:	Mon, 8 Dec 2003 20:18:05 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Memory Management on AMD64 in 32-bit mode
Message-ID:	<20031209011805.GA12260@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3ED686A715B54646AF1BC06C2BFBA4A00167A38D AT kita DOT basistech DOT com>
Mime-Version:	1.0
In-Reply-To:	<3ED686A715B54646AF1BC06C2BFBA4A00167A38D@kita.basistech.com>
User-Agent:	Mutt/1.4.1i
Note-from-DJ:	This may be spam

On Mon, Dec 08, 2003 at 07:30:17PM -0500, Benson Margulies wrote:
>I happen to have access to a an AMD64 system running Windows. All the
>cygwin shells fail to fork with the following. I'd be willing to try
>coding and running a patch if the experts would care to offer an idea of
>what to try.

Sorry but this is not a "now try this" type of debugging activity.  It
would require quite a bit of effort to track this problem down.

As I've said before, it would require physical access to a 64 bit system.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sourceware DOT org
and be permanently blocked from mailing lists at sources.redhat.com

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

- Raw text -