Date: Wed, 25 Feb 2004 21:56:41 +0100 From: Gabriel Ambuehl <gabriel_ambuehl@buz.ch> To: Kris Kennaway <kris@obsecurity.org> Cc: ale@freebsd.org Subject: Re[2]: misc/63213: MySQL 4 crashes on CURRENT since 20040221 Message-ID: <1923328057.20040225215641@buz.ch> In-Reply-To: <20040225031545.GA64456@xor.obsecurity.org> References: <200402221430.i1MEUDpf067186@freefall.freebsd.org> <20040222151553.GA2121@phoenix.smluc.org> <1624691389.20040224193134@buz.ch> <20040225031545.GA64456@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Kris, Wednesday, February 25, 2004, 4:15:45 AM, you wrote: > On Tue, Feb 24, 2004 at 07:31:34PM +0100, Gabriel Ambuehl wrote: >> Hello Erik, >> >> Sunday, February 22, 2004, 4:15:53 PM, you wrote: >> >> > The only thing I did between going from perfectly happy rdbms on >> > -current 20040207 and sig11 spew in an err file was a portupgrade. I >> > tried purging and rebuilding the port a couple times to see if there was >> > build issue, then upgraded world to see if that was the cause... :/ >> > Maybe after I'm done moving and have some time, I'll try to downgrade >> > world to a pre-kse kernel. >> >> MySQL 4.0.18 works perfectly on 5.2.1RC2. I'm now updating to CURRENT >> to see what's going on. > Have you rebuilt all your ports to deal with the libpthread relinking in -CURRENT? Yes. As I said, it works perfectly on 5.2.1RC2, but fails on connects via TCP/IP since at least 2004/02/20 builds (newest cvsup I checked was as of today). (using vanilla make.conf and GENERIC) Fails on both AMD and Via C3 CPUs, no Intel box around, so I can't check that. Best regards, Gabriel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1923328057.20040225215641>