Mail Archives: cygwin/2005/04/14/13:57:17
----Original Message----
>From: Timothy Wall
>Sent: 14 April 2005 18:22
> Attached is a very simple makefile which demonstrates the problem.
> There's a leak either in make itself or in the spawning of
> subprocesses.
>
> Beware! this will likely lock up your machine, or at the very least
> prevent you from launching any new processes.
>
> Simply type "make" with this makefile in the same directory. It
> invokes another target defined within the makefile which does an "echo"
> a couple thousand times.
No, it does it a million times. Well, it does once you rename the file to
'makefile', as otherwise the recursive sub-make doesn't find it because
'makefile.dat' is not one of the default names it looks for. Are you *sure*
you really ran the same test as the one you've sent us?
I've been running it in the background for 45 minutes now and it hasn't
done anything unusual. Looking at the windows task manager, there are no
memory leaks nor handle leaks; none of the figures are steadily increasing,
they're all varying slightly up and down around their resting values. It
does hog a lot of cpu resource and occasionally causes applications to pause
for a while, but it doesn't seem to be doing any real harm.
As to your question, "how do i solve/work around resource temporarily
unavailable", I would have thought it's obvious. You wait a while and try
again later when it isn't unavailable any more.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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/
- Raw text -