[Mingw-notify] [ mingw-Bugs-1335361 ] MSYS shell can not be started on Windows XP Professional x64

[SourceForge.net <no...@so...>]

Bugs item #1335361, was opened at 2005-10-23 13:31
Message generated for change (Comment added) made by nonperson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1335361&group_id=2435

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: msys
Group: IINR - Include In Next Release
Status: Open
Resolution: None
Priority: 5
Submitted By: nonperson (nonperson)
Assigned to: Earnie Boyd (earnie)
Summary: MSYS shell can not be started on Windows XP Professional x64

Initial Comment:
MSYS shell can not be started on Windows XP 
Professional x64. Looking a bit further, rxvt reports
--->
C:\msys\1.0\bin\rxvt.exe: *** fork: can't reserve memory 
for stack 0x480000 - 0x680000, Win32 error 0
      0 [main] rxvt 2928 sync_with_child: child 
1440(0x2CC) died before initialization with status code 
0x1
     43 [main] rxvt 2928 sync_with_child: *** child state 
waiting for longjmp
rxvt: can't fork
rxvt: aborting
<---

I've added a description of some sort of workaround on 
MinGWiki (mSysShell, FAQ). For a better workaround,
the included patch seems to do the trick. It has not been 
tested on 32-bit XP/2K/NT (yet), but it probably works. I 
don't know about 9x/Me either.

I would, however, like to see a fix to make this sort of 
trickery obsolete. (And no, always running 32-bit 
command prompt on your 64-bit OS isn't a fix.)

Of course, an ability to *create* 64-bit executables would 
be even better..


----------------------------------------------------------------------

>Comment By: nonperson (nonperson)
Date: 2005-10-28 20:11

Message:
Logged In: YES 
user_id=1355547

Umm.. Similar meaning that you experience a different error 
on a different OS that is likely to be caused by a different 
thing?

FWIW, I don't have that problem as I'm running Avast! - on 
both 32-bit and 64-bit versions.

----------------------------------------------------------------------

Comment By: Mikhail Grushinskiy (mgrouch)
Date: 2005-10-28 17:07

Message:
Logged In: YES 
user_id=643949

I have very similar problem. My processor is 64 bit (AMD)
but Windows XP is 32.

I've read that it is caused by Norton Antivirus.
Can someone confirm that he was able to resolve this issue
by turning Norton Avtivirus protection off?

Thanks

----------------------------------------------------------------------

Comment By: nonperson (nonperson)
Date: 2005-10-23 13:39

Message:
Logged In: YES 
user_id=1355547

Forgot to say that sh exhibits the same symptoms if run in C:
\MSYS\1.0\bin:
--->
C:\msys\1.0\bin>sh
sh-2.04$ ls
C:\msys\1.0\bin\sh.exe: *** fork: can't reserve memory for 
stack 0x480000 - 0x680000, Win32 error 0
      0 [main] sh 260 sync_with_child: child 264(0x304) died 
before initialization with status code 0x1
     69 [main] sh 260 sync_with_child: *** child state waiting 
for longjmp
sh: fork: Resource temporarily unavailable
sh-2.04$ exit
exit
<---

With 32-bit command prompt it works:
--->
C:\msys\1.0\bin>c:\WIN64\SysWOW64\cmd
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\msys\1.0\bin>sh
sh-2.04$ ls ..
bin  etc   include  lib    man    msys.bat       msys.ico  
uninstall
doc  home  info     m.ico  mingw  msys.bat.orig  share
sh-2.04$ exit
exit

C:\msys\1.0\bin>exit
<---


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1335361&group_id=2435