From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30616 invoked by alias); 16 Feb 2006 17:49:45 -0000 Received: (qmail 30606 invoked by uid 22791); 16 Feb 2006 17:49:44 -0000 X-Spam-Check-By: sourceware.org Received: from cgf.cx (HELO cgf.cx) (24.61.23.223) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 16 Feb 2006 17:49:41 +0000 Received: by cgf.cx (Postfix, from userid 201) id 4AD1A13C0F8; Thu, 16 Feb 2006 12:49:40 -0500 (EST) Date: Thu, 16 Feb 2006 17:57:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygheap base mismatch detected Message-ID: <20060216174940.GL15861@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2006-02/txt/msg00582.txt.bz2 On Thu, Feb 16, 2006 at 01:17:07AM -0600, Dill, Jens (END-CHI) wrote: >Christopher Faylor wrote: >> On Wed, Feb 15, 2006 at 10:22:30PM +0000, Jens Dill wrote: >> >What you write makes it appear that CygWin simply will not support >> >large executables that reference the CygWin DLL and are also launched >> >from a CygWin shell. I can't believe that nobody has found a better >> >workaround than: >> > >> > (a) not using the CygWin DLL (not an option for us) >> > (b) not launching from a CygWin shell (not an option for us) >> > (c) reducing the memory space required by the program (again, not >possible) >> > (d) tinkering randomly with the stack size >> > >> >Does anyone else know of another way around this problem? >> >> How about: >> >> (e) Looking into the source code and coming up with a fix rather than >> a workaround >> >> ? > >Unfortunately for me, (e) is impractical. It's not clear whether it is >my source code or CygWin's that I need to fix, but if it were mine, the >application I am porting to CygWin is really large, and I don't have >the mandate or time to re-architect it as a bunch of small pieces. If >I could do that, I'd rewrite the app for native Windows. If it's the >CygWin source, however interested I may be in fixing it, I have no >mandate from my management to do so (and am not likely to get one). >Furthermore, the problem appears to be something not directly written >into the source but rather a property of the CygWin-Windows >interaction, at a level that I am not likely to understand without >suddenly learning a lot more Windows internals than I ever thought I >would need to (Bet you didn't think there were disadvantages to being a >Unix Guru, did you?). I think you're missing a point here. Your knowledge or management limitations will not have any effect whatsoever on anyone who works on Cygwin. I'm telling you that your best bet is to fix your problem yourself because it is unlikely that anyone else is going to do it for you. I'm not trying to be mean. I'm just telling you what your options are. >My project time frame doesn't allow for that. If I read Dave Korn's >posting correctly (along with the others who talk about adjusting the >sizes of Fortran arrays to fix the problem), it becomes pretty clear to >me that the problem is likely to be one of somehow scaling CygWin to >fit with large executables. Surely someone has run into this before, >and solved it by some other means than either disabling Cygwin or >dismembering their executable. You can use the word "surely" a few more times but it isn't likely that you are going to find a magic bullet for your problem. 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/