X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Shankar Unni Subject: Re: _kbhit Date: Fri, 17 Feb 2006 12:27:52 -0800 Lines: 17 Message-ID: References: <20060216011405 DOT 9CC6E2681 AT dot DOT warande DOT net> <001e01c632af$25414d20$020aa8c0 AT DFW5RB41> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051201 Thunderbird/1.5 Mnenhy/0.7.3.0 In-Reply-To: <001e01c632af$25414d20$020aa8c0@DFW5RB41> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Gary R. Van Sickle wrote: > Arend-Jan Westhoff writes: >> I cannot confirm your assertion that msvcrt.dll and >> cygwin1.dll cannot be used together. > The Gary Exclusion Principle: Two C runtimes cannot occupy the same point > in space at the same moment in time. The problem here is that unfortunately they *can* occupy the same point in space at the same time, with the same bad effects as in science fiction movies when one object materializes in the middle of another :-). The problem is that, for instance, some of your malloc calls will link to the cygwin libc, while others (from within the Windows DLLs) will link to MSVCRT, and if you free the pointer with the "other" library, terrible things will happen. -- 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/