Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Bug identified [was RE: perl - segfault on "free unused scalar"]
Date: Thu, 28 Jul 2005 15:05:07 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.GSO.4.61.0507280954380.27026@slinky.cs.nyu.edu>
Message-ID: <SERRANOiSzuaWSnlsIh00000034@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Igor Pechtchanski
>Sent: 28 July 2005 14:58



> Hmm, but shouldn't this code fail regardless of the value of
> heap_chunk_in_mb?  Why does increasing heap_chunk_in_mb make this succeed?

  Perhaps it only makes it succeed if you increase heap_chunk_in_mb until
that initial heap chunk is big enough?  Perhaps just because the memory map
gets re-arranged and dll_list::alloc manages to find a page in between the
dll and the heap?  You could always check it out in a debugger if you like;
I've got to leave this for the moment because I was doing that in my
lunchbreak, which is long over now :-(


    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/