From owner-freebsd-hackers Mon Feb 22 0: 9:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.dyn.ml.org (pm3-22.ppp.wenet.net [206.15.85.22]) by hub.freebsd.org (Postfix) with ESMTP id 40ADA11B46 for ; Mon, 22 Feb 1999 00:09:15 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id AAA01057; Mon, 22 Feb 1999 00:07:43 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Mon, 22 Feb 1999 00:07:43 -0800 (PST) From: Alex Zepeda To: Amancio Hasty Cc: hackers@FreeBSD.ORG Subject: Re: gcc 2.8.1 Exceptions? In-Reply-To: <199902220443.UAA88362@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Feb 1999, Amancio Hasty wrote: > Exception handling appears to work with the stock gcc... Uhh I don't think so. That's one of the selling points of gcc 2.8 or newer. To get exception handling working you'll need to use -fsjlj-exceptions (setjmp/longjmp exceptions). If you need thread safe exceptions, get egcs 1.1.1, and use the various startup objects from it (and then you can ditch -fsjlj-exceptions). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message