This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Ronald van Gogh <rogonl at hotmail dot com>
- Cc: cygwin at cygwin dot com
- Date: Thu, 23 Oct 2003 11:52:53 -0400 (EDT)
- Subject: Re: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
- References: <LAW11-F71hn65DWG6tA00003349@hotmail.com>
- Reply-to: cygwin at cygwin dot com
Ronald,
On Thu, 23 Oct 2003, Ronald van Gogh wrote:
First of all, sorry, but I still don't know how to post a reply, since I'm
registered on the mailinglist in digestmode and nobody seems to be able to
tell how to reply on a single mail I see in this list of mails.
I don't think the hotmail web interface is sophisticated enough to allow
you to do this. Other mailers, like pine, will present each message in
the digest as an attachment to the main digest message, and you'll be able
to reply to any of them. I know there's a script around for fetching
Yahoo! mail messages in mbox format, so you can use pine locally on your
machine. No doubt there's a similar one for hotmail somewhere.
This problem becomes very urgent to us. If we can't fix it we might have to
look for alternatives !
As I've told before we're collecting information on a dominoserver every 10
minutes by running a bash script (cygwin) scheduled by Windows Scheduler
(Splinterware).
Any particular reason you're not using cron?
We noticed that sometimes (once or twice a day) this failed.
To check the cause we created a new small shell script, which only writes a
date and time to a file.
You might want to try writing the output of "cygcheck -svr" to the output
file from that script as well.
Furthermore, to catch any stdout/stderr messages, we called the script
by a batch file.
Huh? Why do you need a batch file to catch stderr messages? I must be
missing something.
The sources of both programs are described below.
schedule_chk.bat
-----------------------
@echo off
d:\cygwin\bin\bash.exe --login -i
"d:/Lotus/Domino/Data/StatCollect/bin/schedule_chk.sh"
>>d:\cygwin\tmp\schk.txt 2>&1
schedule_chk.sh
-----------------------
#!/usr/bin/ksh
echo $(date) >> /tmp/schedule_chk.log
This generated the following outputfiles (the file schk.txt contains the
errors):
schedule_chk.log
------------------------
Tue Sep 30 08:00:01 2003
Tue Sep 30 08:10:01 2003
Tue Sep 30 08:20:01 2003
Tue Sep 30 08:30:01 2003
Tue Sep 30 08:40:01 2003
Tue Sep 30 08:50:01 2003
Tue Sep 30 09:00:01 2003
Tue Sep 30 09:10:01 2003
Tue Sep 30 09:30:00 2003
Tue Sep 30 09:40:00 2003
Tue Sep 30 09:50:00 2003
Tue Sep 30 10:00:00 2003
Tue Sep 30 10:10:01 2003
Tue Sep 30 10:30:00 2003
schk.txt
-----------
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 384, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 384, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 384, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 384, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 384, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 384, Win32 error 0
d:\cygwin\bin\bash.exe: *** unable to allocate heap, heap_chunk_size 0, Win32 error 0
As you can see the log file sometimes contains gaps and errormessages are
written to stderr.
You should be able to detect this situation by the return code from bash,
and write the output of "cygcheck -svr" only in the failing cases.
Another possibility is running this under strace, waiting for it to fail,
and, if it failed, saving the strace output and looking through that.
I've attached a cygcheck.out file for more information.
Kind regards, Ronald van Gogh
Hope this helps,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/