sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487

2010-04-09 Thread Ricardo Urbina
Hi. Last tuesday I updated my Cygwin installation from 1.7.1 to 1.7.4. And then I started getting these errors when running a perl script: % perlscript 3 [main] sh 11716 C:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x85, top 0x89, reserve_size

Re: sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487

2010-04-12 Thread Ricardo Urbina
On Mon, Apr 12, 2010 at 4:03 AM, Reini Urban wrote: > 2010/4/9 Ricardo Urbina: >> Hi. Last tuesday I updated my Cygwin installation from 1.7.1 to 1.7.4. >> And then I started getting these errors when running a perl script: >> >> % perlscript >>      3 [ma

Re: sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487

2010-04-23 Thread Ricardo Urbina
g run than viruses would. They can't detect a 0-day virus, but they do slow down and stop a lot of legitimate stuff. But for us who are chained to MS, Cygwin is an oasis in the middle of the desert. On Mon, Apr 12, 2010 at 9:44 AM, Ricardo Urbina wrote: > On Mon, Apr 12, 2010 at 4:

Re: sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487

2010-04-23 Thread Ricardo Urbina
Ditched Symantec, good. But now Kaspersky says xinetd is piping data, and piping data is a potential RootKit risk. Oh, the humanity!! Lesson learned: spare yourself a headache, trust the BLODA. On Fri, Apr 23, 2010 at 10:55 AM, Ricardo Urbina wrote: > I fixed this yesterday. Just for the rec

Ctrl+Space not working under Windows Terminal

2022-09-02 Thread Ricardo Urbina
Hi, I'm trying out Cygwin's Zsh within Windows Terminal because WT integrates better with WSL, but Cygwin beats it for working on the Windows side. However, I launched emacs and eventually noticed that Ctrl+Space doesn't work when running under Windows Terminal. It doesn't work on jmacs, and using