From owner-freebsd-current Sat Apr 3 15:12: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-33.ppp.wenet.net [206.15.85.33]) by hub.freebsd.org (Postfix) with ESMTP id 822F714E6C for ; Sat, 3 Apr 1999 15:12:03 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id PAA13852; Sat, 3 Apr 1999 15:10:22 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 3 Apr 1999 15:10:22 -0800 (PST) From: Alex Zepeda To: Amancio Hasty Cc: current Subject: Re: X problems using egcs as compiler In-Reply-To: <199904032244.OAA57143@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Amancio Hasty wrote: > Yes, it is most likely a DWARF2_UNWIND issue at least that is what I > concluded in trying to support Electric Fire also someone should > investigate whether egcs supports exception handling without thread > support if memory does not fail me egcs requires thread support for > exception handling. Perhaps it is a good time to review the egcs docs > with respect to frame handling and exception handling. How can I tell if I've got thread support enabled? I've used ksirc before which uses exceptions to parse irc output, and it's obviously not threaded (cause Qt isn't). Sure, I don't like ksirc, and I got some odd perl related errors, but it worked. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message