This is the mail archive of the
mailing list for the Cygwin project.
Re: sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487
<rant>Ditched Symantec, good. But now Kaspersky says xinetd is piping
data, and piping data is a potential RootKit risk. Oh, the
Lesson learned: spare yourself a headache, trust the BLODA.
On Fri, Apr 23, 2010 at 10:55 AM, Ricardo Urbina
> I fixed this yesterday. Just for the record: Symantec Endpoint
> Protection, and they had updated it the night before my troubles
> began. Can't help that, I'm at work. But they ditched SEP yesterday
> and my cygwin fixed automagically, yay!
> Nowadays I think anti-viruses cost more on the long 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: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 [main] sh 11716 C:\cygwin\bin\sh.exe: *** fatal error -
>>>> couldn't allocate heap, Win32 error 487, base 0x850000, top 0x890000,
>>>> reserve_size 258048, allocsize 262144, page_const 4096
>>>> Â Â Â2 [main] sh 10172 fork: child -1 - died waiting for longjmp
>>>> before initialization, retry 0, exit code 0x100, errno 11
>>> First I need a http://cygwin.com/problems.html report
>>> Second, you can try a lower rebase address, as pointed out in
>> I didn't know there was a perlrebase. It didn't change a thing. I'm
>> starting to think it's not a cygwin issue: after perlrebase, it ran
>> just fine once. Then the whole system crashed. It didn't work again
>> after rebooting. Anyway, I attach my cygcheck output. Thanks a lot!
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple