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: Mon, 15 Aug 2005 22:03:29 -0700 From: Yitzchak Scott-Thoennes To: cygwin@cygwin.com Subject: Re: Cygwin.dll crash, alloca and custom stack Message-ID: <20050816050328.GA2136@efn.org> References: <602EF4562299D711978800065BEECE9A0D2D30D4@cbrml50.ag.gov.au> <20050816023131.145D21701FA@samwise.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050816023131.145D21701FA@samwise.efn.org> User-Agent: Mutt/1.4.2.1i X-IsSubscribed: yes On Mon, Aug 15, 2005 at 09:31:12PM -0500, Gary R. Van Sickle wrote: > Is there going to be any part of this interpreter that isn't a "no-no"? > You're going to longjmp() around all your crazy malloc'd stacks? Seriously > Chris, how is it that you can come up with all these wild... Schemes... and > yet you can't just admit you've taken a wrong turn at Albequerque and do > things in a sane way? No, it's perl that longjmps around crazy malloc'd stacks. But at least it doesn't set registers to them, and is slow as molasses because of it. -- 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/