Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-pair-Authenticated: 24.126.76.52 Message-ID: <41E53D86.2070605@kegel.com> Date: Wed, 12 Jan 2005 07:08:54 -0800 From: Dan Kegel User-Agent: Mozilla/4.0 (compatible;MSIE 5.5; Windows 98) MIME-Version: 1.0 To: Rainer Hochreiter CC: cygwin AT cygwin DOT com, crossgcc AT sources DOT redhat DOT com Subject: Re: c++ exceptions in shared library results in crash References: <32235 DOT 193 DOT 16 DOT 155 DOT 145 DOT 1105531282 DOT squirrel AT 193 DOT 16 DOT 155 DOT 145> In-Reply-To: <32235.193.16.155.145.1105531282.squirrel@193.16.155.145> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Rainer Hochreiter wrote: > now my problem: > i created a main program and a shared library, both written in c++, where > the source is parially taken from the "c++ dlopen mini howto". > > find the sources in the attachments! > > throwing an exception in the shared library results in a core dump of the > binary executable - but only for the cross-compiled version! > > the native linux and cygwin compiled versions work. > so, could someone give me a hint, what's wrong with my cross-compiler? > > my cross-compiler (verson 3.2.3) runs under linux and creates cygwin > executables. Where did you get your cross-compiler? It may have been poorly built. Alternately, maybe it's simply mismatched with the native Cygwin compiler; you might try using the same version of gcc as Cygwin uses. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html -- 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/