{"id":2252,"date":"2009-05-24T18:58:26","date_gmt":"2009-05-24T18:58:26","guid":{"rendered":"http:\/\/t.motd.kr\/articles\/2252\/cygwin-bash-fatal-error-in-windows-64-bit-command-prompt-or-puttycyg"},"modified":"2022-12-28T01:45:05","modified_gmt":"2022-12-27T16:45:05","slug":"cygwin-bash-fatal-error-in-windows-64-bit-command-prompt-or-puttycyg","status":"publish","type":"post","link":"https:\/\/vault.motd.kr\/wordpress\/posts\/2252\/cygwin-bash-fatal-error-in-windows-64-bit-command-prompt-or-puttycyg\/","title":{"rendered":"Cygwin Bash Fatal Error in Windows 64-bit Command Prompt or PuTTYcyg"},"content":{"rendered":"\n
In Windows 7 RC x64, you will get the following fatal memory allocation error if you launch Cygwin (bash) from the comment prompt:<\/p>\n\n\n\n
2 [main] bash 2776 C:\\Cygwin\\bin\\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0xF20000, top 0xF90000, reserve_size 454656, allocsize 458752, page_const 4096<\/code><\/pre>\n\n\n\nThis error can be worked around by using x86 (32-bit) version of the command prompt. That is, instead of executing C:\\WINDOWS\\SYSTEM32\\CMD.EXE<\/code> (the 64-bit binary), you have to execute C:\\WINDOWS\\SYSWOW64\\CMD.EXE<\/code> (the 32-bit binary).<\/p>\n\n\n\nFor example, to launch a bash shell in the command prompt window, you have to execute the following command instead of executing the bash.exe<\/code> directly:<\/p>\n\n\n\nC:\\WINDOWS\\SYSWOW64\\CMD.EXE \/C C:\\Cygwin\\bin\\bash.exe<\/code><\/pre>\n\n\n\nActually, you might not have experience this issue if you were using PuTTYcyg version 20090212 or above<\/a>. I was using an older version cluelessly.<\/p>\n\n\n\n\uc708\ub3c4\uc6b0\uc988 7 RC x64\uc5d0\uc11c \uc2dc\uadf8\uc708 (\ubc30\uc26c\uc258) \uc744 \uba85\ub839\ud589\uc5d0\uc11c \uc2e4\ud589\ud558\uba74 \ub2e4\uc74c\uacfc \uac19\uc740 \uce58\uba85\uc801 \uba54\ubaa8\ub9ac \ud560\ub2f9 \uc5d0\ub7ec\uac00 \ubc1c\uc0dd\ud569\ub2c8\ub2e4:<\/p>\n\n\n\n
2 [main] bash 2776 C:\\Cygwin\\bin\\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0xF20000, top 0xF90000, reserve_size 454656, allocsize 458752, page_const 4096<\/code><\/pre>\n\n\n\n\uc774 \uc5d0\ub7ec\ub294 \uba85\ub839\ud589\uc758 x86 (32 \ube44\ud2b8) \ubc84\uc804\uc744 \uc0ac\uc6a9\ud574\uc11c \ud574\uacb0\ud560 \uc218 \uc788\uc2b5\ub2c8\ub2e4. \uc989, C:\\WINDOWS\\SYSTEM32\\CMD.EXE<\/code> (64 \ube44\ud2b8 \ubc14\uc774\ub108\ub9ac) \ub300\uc2e0 C:\\WINDOWS\\SYSWOW64\\CMD.EXE<\/code> (32 \ube44\ud2b8 \ubc14\uc774\ub108\ub9ac) \ub97c \uc2e4\ud589\ud558\uba74 \ub429\ub2c8\ub2e4.<\/p>\n\n\n\n\uc608\ub97c \ub4e4\uc5b4, \uba85\ub839\ud589 \ucc3d\uc5d0\uc11c \ubc30\uc26c \uc258\uc744 \uc2e4\ud589\ud558\ub824\uba74, bash.exe<\/code> \ub97c \uc9c1\uc811 \uc2e4\ud589\ud558\ub294 \ub300\uc2e0 \ub2e4\uc74c \uba85\ub839\uc744 \uc2e4\ud589\ud574\uc57c \ud569\ub2c8\ub2e4:<\/p>\n\n\n\nC:\\WINDOWS\\SYSWOW64\\CMD.EXE \/C C:\\Cygwin\\bin\\bash.exe<\/code><\/pre>\n\n\n\n\uc0ac\uc2e4 PuTTYcyg \ubc84\uc804 20090212 \uc774\uc0c1<\/a> \uc744 \uc0ac\uc6a9\ud558\uace0 \uacc4\uc168\ub2e4\uba74 \uc774 \ubb38\uc81c\ub97c \uc804\ud600 \uacaa\uc9c0 \uc54a\uc73c\uc168\uc744 \uc218\ub3c4 \uc788\uc2b5\ub2c8\ub2e4. \uc800\ub294 \uadf8\uac83\ub3c4 \ubaa8\ub974\uace0 \uc608\uc804 \ubc84\uc804\uc744 \uc0ac\uc6a9\ud558\uace0 \uc788\uc5c8\uac70\ub4e0\uc694.<\/p>\n","protected":false},"excerpt":{"rendered":"In Windows 7 RC x64, you will get the following fatal memory allocation error if you launch Cygwin (bash) from the comment prompt: This error can be worked around by using x86 (32-bit) version of the command prompt. That is, instead of executing C:\\WINDOWS\\SYSTEM32\\CMD.EXE (the 64-bit binary), you have to execute C:\\WINDOWS\\SYSWOW64\\CMD.EXE (the 32-bit binary)…. Continue reading