Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 28 Jul 2005 01:33:02 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Krzysztof Duleba cc: cygwin AT cygwin DOT com Subject: Re: perl - segfault on "free unused scalar" In-Reply-To: Message-ID: References: <42E76865 DOT 4000301 AT familiehaase DOT de> <42E7B413 DOT 8040203 AT familiehaase DOT de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 28 Jul 2005, Krzysztof Duleba wrote: > Igor Pechtchanski wrote: > > > > 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")... > > I am not. I understand that this is how it should work theoretically, > but I've _checked_ that on a couple of Cygwin boxes with different > versions of cygwin1.dll and gcc. All of them didn't really care that > heap_chunk_in_mb was undefined in the registry. Perl, on the other hand, > do care. Actually, you're right. Perhaps it depends on what kind of malloc the program uses (i.e., whether it uses the Cygwin builtin malloc, or something else). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,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/