What is more : sometimes I get the same type of messages on
an Intel Xeon based system.
I think that I have a chance of 1 in 500 before I get the same
problem, and this is with a program which forks several
subprocesses and enters a loop with ticks of 1 s for waiting on
finished processes and launching another one.
I think it is more an error in the operating system, which may
get worse by running on AMD.
Regards,
Jurgen
Christopher Faylor <[EMAIL PROTECTED]>
Sent by:
[EMAIL PROTECTED]
12/09/2003 02:18 AM
Please respond to cygwin
To: [EMAIL PROTECTED]
cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS)
Subject: Re: Memory Management on AMD64 in 32-bit mode
Classification:
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 [EMAIL PROTECTED]
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/
--
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/
