#667 Can't reserve space for heap

closed-fixed
nobody
MSYS (75)
2011-01-19
2004-10-20
No

When attempting to run rxvt, I get the following and
rxvt, of course, doesn't execute:

m.AllocationBase 0x0, m.BaseAddress 0x715B0000,
m.RegionSize 0x160000, m.State 0x10000
C:\msys\1.0\bin\rxvt.exe: *** Couldn't reserve space
for cygwin's heap (0x715B0000 <0xF10000>) in child,
Win32 error 6

Win32 erorr 6 appears to be an invalid handle. I'm
happy to attempt to look in the source code, if only I
had a clue where to start. I'm using the Current
release, downloaded about two days ago. Cygwin is
installed, but not present in PATH.

Discussion

  • Scott Michel

    Scott Michel - 2004-10-26
    • priority: 5 --> 7
     
  • Earnie Boyd

    Earnie Boyd - 2004-10-27

    Logged In: YES
    user_id=15438

    Do you have the CYGWIN environment variable set? I seem to
    remember something from long past about a problem from the
    contents of the CYGWIN variable that could cause this.

    Earnie

     
  • Scott Michel

    Scott Michel - 2004-10-27

    Logged In: YES
    user_id=52148

    No CYGWIN environment variable set, PATH is set to the
    minimal path possible
    (\WINNT\SYSTEM32;\WINNT;\WINNT\SYSTEM32\Wbem).

     
  • Scott Michel

    Scott Michel - 2004-10-27

    Logged In: YES
    user_id=52148

    I've perused the winsup/cygwin/cygheap.cc source code, and
    nothing seems to immediately spring to forefront as an
    obvious reason why the cygwin heap allocation fails.

    However, there's a glaring problem in that code: another
    call to a Win32 method occurs overwriting GetLastError()
    (the "%E" format spec). So the actual reason why the call is
    failing is masked.

    I can't recompile, for obvious reasons, to examine the bug
    further.

     
  • Scott Michel

    Scott Michel - 2004-10-27
    • labels: 104601 --> MSYS
     
  • Scott Michel

    Scott Michel - 2004-11-03

    rt/src/winsup/cygwin/cygheap.cc patch

     
  • Scott Michel

    Scott Michel - 2004-11-03

    Logged In: YES
    user_id=52148

    I've "upgraded" to the latest msys snapshot -- same problem.
    It would be helpful to diagnose the problem if the attached
    patch were applied to cygheap.cc in the next snapshot. The
    Win32 error code doesn't make any sense (there's no "handle"
    being passed to VirtualAlloc), so the Win32 error code
    should be printed just after VirtualAlloc fails.

     
  • Scott Michel

    Scott Michel - 2011-01-19
    • status: open --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks