X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Message-ID: <4C1A2BBA.6080805@cwilson.fastmail.fm> Date: Thu, 17 Jun 2010 10:05:46 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: C++ app segfaults in libstdc++ References: <4C198B44.6040803@cwilson.fastmail.fm> <4C1A11EF.9000405@gmail.com> <4C1A2829.3090602@gmail.com> In-Reply-To: <4C1A2829.3090602@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 On 6/17/2010 9:50 AM, Dave Korn wrote: > To summarize the summary of the summary: C++ is complicated. No kidding. What if the datatypes used in the interface between the module and main -- including ALL exception classes -- were defined in a second DLL, on which both module and main depend? Then module could be dynamically loaded (and unloaded), without any 'static' entanglments with main. But...I'm not sure if that would fix the problem you described in your first reply, since module would have created the modexc instance, even if the class is defined in another DLL. I'll give it a try later on. -- Chuck -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple