What approach is being used in 1.3.7 or what module is responsible for this in the cygwin1.dll? We use DLLs quite a bit and have experimented with a variety of mechanisms to detect similar forms of DLL conflict. A small amount of shared memory DLL intercommunication might work very nicely, although the trick of course is detecting the really old stuff out their that people include with their applications. I've seen a lot of open source computational chemistry software that includes the cygwin1.dll. What is your architectural approach to this right now?
Larry Wood -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor Sent: Saturday, January 12, 2002 11:25 PM To: [EMAIL PROTECTED] Subject: Re: Windows XP and cygwin's heap On Sat, Jan 12, 2002 at 11:28:48PM -0500, Laurence F. Wood wrote: >I have seen this problem before caused by conflicting cygwin1.dll files. >Why not modify cygwin1.dll to detect the presence of conflicting cygwin1.dll >files and report this to the user in an informative way. Well, duh. There is already some detection in the DLL. There will be more in 1.3.7. Or, were you going to contribute something? If so, I'll hold off the release so that we can get your changes in. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/