From owner-freebsd-stable Wed Dec 6 9: 9:26 2000 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 6 09:09:24 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D310937B400 for ; Wed, 6 Dec 2000 09:09:23 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA21411; Wed, 6 Dec 2000 09:07:58 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id eB6H7v730385; Wed, 6 Dec 2000 09:07:57 -0800 (PST) (envelope-from jdp) Date: Wed, 6 Dec 2000 09:07:57 -0800 (PST) Message-Id: <200012061707.eB6H7v730385@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Reply-To: stable@freebsd.org Cc: fjoe@iclub.nsu.ru Subject: Re: Mysql segfaults; is the culprit libstdc++, pthread, regex ...? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: jdp@wall.polstra.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > now I can confirm that on latest -stable without "linking shared > objects with libgcc_[r]_pic" changes ACE wrappers tests run > correctly without segfaults. test program ("bad" one) from PR/23252 > also does not segfault anymore. Excellent sleuthing from Max, as always. Thanks! > and yes, seems that anything using C++ and threads is broken in > 4.2-RELEASE :( I think that changes to compiler and binutils should > be tested in -current for much longer period of time before MFC and > should be MFC'ed long before release date. Fair enough. And as the person who urged that libgcc be linked into all shared libraries, I'll take the blame for this one. It was the classic fix-a-bug-and-create-a-new-bug syndrome. The reason for the addition of libgcc was to fix a backward-compatibility bug introduced when we made exceptions work right. And the reason we rammed the exceptions fix into 4.2 was because a bunch of folks (including *cough* you, Max, if I remember correctly) told us in no uncertain terms that we just HAD to fix that before 4.2 was released. It's hard to know how to resolve that kind of conflict without simply slipping the release date -- which was not an option, according to Jordan. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message