On Thu, 28 Jul 2005, Krzysztof Duleba wrote:
> Igor Pechtchanski wrote:
> > On Wed, 27 Jul 2005, Krzysztof Duleba wrote:
>
> > > I've simplified the test case. It seems that Cygwin perl can't handle
> > > too much memory. For instance:
> > >
> > > $ perl -e '$a="a"x(200 * 1024 * 1024); sleep 9'
>
> > > $ perl -e '$a="a"x(1024 * 1024);my %b; $b{$_}=$a for(1..400);sleep 9'
>
> > > $ perl -e '$a="a"x(50 * 1024 * 1024);$b=$a;$c=$a;$d=$a;$e=$a;sleep 10'
> >
> > Yeah. Set heap_chunk_in_mb to include all available memory, and I'm sure
> > you'll find that Cygwin perl works the same too.
>
> After setting heap_chunk_in_mb to 2048, all those tests passed. Thanks! But I
> still don't understand why C isn't bound by heap_chunk_in_mb and perl is.
I think you're confused. All Cygwin programs, including those written in
C, are bound by heap_chunk_in_mb. Unless you are somehow generating a
pure Windows program from your C source (e.g., using "gcc -mno-cygwin")...
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED]
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA
--
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/
