This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: bash on NT 4.0 (was forkee heap_init)
- To: "gnu-win32 at cygnus dot com" <gnu-win32 at cygnus dot com>, "'Jeff Oh'" <jeffoh at zadall dot com>
- Subject: RE: bash on NT 4.0 (was forkee heap_init)
- From: Brian Beuning <BrianB at atl dot paysys>, com at cygnus dot com
- Date: Mon, 28 Apr 1997 09:03:32 -0400
Jeff,
I have been running bash on two different NT 4.0 systems.
One with a p5-166 and NT 4.0 (build 1381) and one a dual
p6-150 with NT 4.0 (unknown build level).
Good Luck,
Brian
----------
From: Jeff Oh
Sent: Friday, April 25, 1997 12:14 PM
To: gnu-win32@cygnus.com
Subject: bash on NT 4.0 (was forkee heap_init)
Despite several good suggestions from this list, I have not been able
to determine why bash is generating the forkee heap_init error 487
(this actually happens in the cygwin.dll code, when the child process
uses virtual_alloc() to try and reserve a memory block at the same
base address as it's parent.) Unfortunately, I can't compile debug
versions of the shell or cygwin.dll, since I need to run configure
to do so, and I need a working shell to run configure, and bash
isn't working, and.....
So, as no one else on the list seems to be having this problem, and
I get this problem on two separate NT 4.0 systems that I've tried,
but on WIN95, is anyone else running bash successfully on a NT 4.0
system of any flavour (but especially build 1381, service pack 2)?
Alternatively, while I would prefer to use bash, assuming that I cannot
make bash work, has anyone on the list looked at or evaluated other
sh or ksh variants for NT.
Thanks,
Jeff 8-)
--
Jeff Oh, Zadall Systems Group. jeffoh@zadall.com 8-)
"Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning." -- Rich Cook
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".