Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Sun, 25 Aug 2002 14:03:46 +0200 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere X-Priority: 3 (Normal) Message-ID: <173766485377.20020825140346@familiehaase.de> To: cygwin@cygwin.com Subject: Re: Xerces C++ support in cygwin In-Reply-To: <004801c24bf1$95216330$0200a8c0@TCS012593> References: <20020823154437.6154.h011.c000.wm@mail.backus.com.criticalpath.net> <29727752142.20020825031813@familiehaase.de> <004801c24bf1$95216330$0200a8c0@TCS012593> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hallo Abraham, > Now the tests and samples build ok, but when I try to run the tests, I get a > stackdump. It appears that either gcc or cygwin has a problem with c++ > exceptions being thrown from a dll. I stepped through the DOMMemTest app in > gdb and it puked at about the moment where a DOMException would be thrown. > I've seen some mention of this c++ exceptions problem in the cygwin mailing > list archives, but don't see any solutions or further ideas about where the > problem lies, although I thought I saw mention somewhere that the problem > exists in other platforms besides cygwin when gcc is used. I remember, I got this problem too when I got it it to compile the first time (some assert statement). Doesn't this happen in the DLL, and therefore affects all executables linked against it? Gerrit -- perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);' -- 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/