Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 28 Jul 2005 20:45:46 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Bug identified [was RE: perl - segfault on "free unused scalar"] Message-ID: <20050729004546.GC1210@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <42E9594A.8020703@familiehaase.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42E9594A.8020703@familiehaase.de> User-Agent: Mutt/1.5.8i On Fri, Jul 29, 2005 at 12:16:42AM +0200, Gerrit P. Haase wrote: >Dave, > >Some comments on your analysis. > >The latest perl uses auto-image-base and the base address should be >different than default. It fails anyway. > >Perl uses its own malloc, rebuilding with the system malloc shows >that it behaves similar than the C examples, I think the recent >changes in Cygwin do what they should do: make setting the heap >size superflous. Could someone point to what these changes are that are supposed to make setting the heap size irrelevant? Dave mentioned "cygload". I don't really know what that is, unless it has something to do with the minor changes made to get cygwin somewhat working when loaded dynamically. I'm not really aware of any changes which would make setting the heap size irrelevant. cgf -- 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/