From owner-freebsd-hackers Fri Aug 25 7: 5:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 992A837B423 for ; Fri, 25 Aug 2000 07:05:10 -0700 (PDT) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.0/8.11.0) id e7PE2KG06553; Fri, 25 Aug 2000 10:02:20 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 25 Aug 2000 10:02:20 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: Max Khon Subject: Re: Document about threads Cc: freebsd-hackers@FreeBSD.ORG, "Bryan K. Ogawa" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > this issue is unrelated to threads. FreeBSD stock g++ 2.95.2 compiler > uses -fsjlj-exceptions mechanism for exception handling which is broken > (g++ sometimes generates incorrect code even without any optimization > options given). It is not FreeBSD-specific behaviour. gcc GNATS has > bug report with similar gcc behaviour under OS/390. There was a bug in -fsjlj-exceptions code generation related to shared libraries and to best of my knowledge the correct fix has been imported into the official gcc CVS tree and was merged into FreeBSD some time ago. Are there any other errors you know about? If there are any simple code snippets which can demonstrate the problem, I am willing to investigate it further and see if it can be fixed. -fsjls-exceptions errors should be fixed regardless of whether FreeBSD is going to switch to DWARF scheme or not. 4.x-STABLE is here to stay for quite some time and I doubt that it will ever be changed to use DWARF unwinding. ------------------------------------------ E-Mail: Alexander N. Kabaev Date: 25-Aug-00 Time: 09:45:59 ------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message