From owner-freebsd-current Mon Jan 17 10:29:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 938CA14EEC; Mon, 17 Jan 2000 10:29:02 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-13.iptelecom.net.ua [212.9.226.141]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id UAA24663; Mon, 17 Jan 2000 20:33:45 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id UAA07008; Mon, 17 Jan 2000 20:28:28 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38835F47.FE17BF29@altavista.net> Date: Mon, 17 Jan 2000 20:28:23 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Alexander N. Kabaev" Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: C++ exceptions doesn't work in shared libraries References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alexander N. Kabaev" wrote: > As promised, I tried to look into the problem little futher. The following > patch fixes all crashes for me and I was unable to reproduce the bug anymore. I > would really like to hear if it works for you too. I am especially interested > to know if it works on Alpha, because I cannot test it myself. > > PS. The code in question is in mashine independent, so I have reason to believe > that this patch may fix the problem for other platforms too... > > Index: contrib/gcc/except.c > =================================================================== > RCS file: /home/ncvs/src/contrib/gcc/except.c,v > [Nice patch stripped] Yeah, it works! (at least at a first glance). David, what do you think about it? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message