From owner-freebsd-questions@FreeBSD.ORG Sat Sep 30 21:11:10 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 004E216A40F for ; Sat, 30 Sep 2006 21:11:09 +0000 (UTC) (envelope-from SRS0=eaBS/VOT=DN=asarian-host.net=admin@asarian-host.net) Received: from mail.asarian-host.net (mail.asarian-host.net [194.109.160.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50AF143D45 for ; Sat, 30 Sep 2006 21:11:08 +0000 (GMT) (envelope-from SRS0=eaBS/VOT=DN=asarian-host.net=admin@asarian-host.net) Received: from anonymizer.asarian-host.net (localhost [127.0.0.1]) (authenticated bits=0) by mail.asarian-host.net (8.13.5/8.13.5) with ESMTP id k8ULB7kh057406 for ; Sat, 30 Sep 2006 23:11:07 +0200 (CEST) (envelope-from admin@asarian-host.net) From: Mark Received-SPF: pass (asarian-host.net: 127.0.0.1 is authenticated by a trusted mechanism) receiver=anonymizer.asarian-host.net; client-ip=127.0.0.1; envelope-from=; helo=clientrunner.asarian-host.net; Message-Id: <200609302111.k8ULB3jU057396@asarian-host.net> Date: Sat, 30 Sep 2006 21:11:07 GMT X-Authenticated-Sender: admin@asarian-host.net X-Trace: DJ7AgiLBM+RTdBUkQxKT0L9h06bU+s1D7tFMImZNGvgL30tRSF1sR5duIpjG0Mxv X-Complaints-To: abuse@asarian-host.net X-Abuse-Info: Please be sure to forward a copy of ALL headers, otherwise we are unable to process your complaint Organization: Asarian-host To: "'FreeBSD-Questions Questions'" MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 In-Reply-To: <451EB059.1030005@dial.pipex.com> X-Auth: Asarian-host PGP signature iQEVAwUARR7dazFqW1BleBN9AQETfQgAirxHWZkXy5pSamvN3DMaRXfiNbUm5IBq 9gjUnHdnss4EX21XjQkwuJal21SLCDqAEHx6QoS9O2xb/WtSNBHVU0jXwBIJm3Wv STdi2ubgeRfKfC1e7Hfze8WIdx3K5FhDI6jmU+NDd6CrJ15OTwoeg19QGjAp2j2o t/2K7xDf/161/eSu/ILi6pPHpBnTG9/O8LFP9/z2SZGcRMvE4oq2aDswrw5VCYNk g98/hDk6SsfBvExzpjoA9kRJ4DBBWCoCYoPyYoHGcKlQADypi2MLb0M2xR+kAtJ6 7rMGTgh6eYn1jkR1/IOJg+8WWp4mx3Jz/Te0CCjWIFPdb0DS3Dh+Sg== =AVEK Subject: RE: Trouble with Berkeley DB version 4.4.20? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 21:11:10 -0000 > -----Original Message----- > From: Alex Zbyslaw [mailto:xfb52@dial.pipex.com] > Sent: zaterdag 30 september 2006 20:14 > To: Mark > Cc: 'FreeBSD-Questions Questions' > Subject: Re: Trouble with Berkeley DB version 4.4.20? > > > I have done this upgrade path for BerkeleyDB and Perl several times; > > from 1.85 -> 4.1 -> 4.2, and now -> 4.4.20. It has always worked well. > > Even now it compiles just fine. It just isn't stable anymore. > > > > If someone out there has an idea, I'd really like to know. > > I don't have any good answers for you, sorry. Probably no-one is answer- > ing because no-one active is doing anything with these particular pack- > age versions. > > But, there is a port of BerkeleyDB (databases/p5-BerkeleyDB) which would > save you from having to mess around configuring config.in yourself. Just > set something like WITH_BDB_VER=44 (or 42 or...) in pkgtools.conf (for > portupgrade) or make.conf or on the command line. The port doesn't seem > to do any local patches so I wouldn't expect it to work any better for > you, unless you have been doing something wrong. Thanks for answering. Really appreciate it. I actually already tried p5-BerkeleyDB too. Had high hopes for it. It took a good 10 minutes or so to compile a new gcc, 3.2.23, first; but after that, everything went well. Except that it shows the same behavior. Compile goes fine; "make tests" too. But my app core dumps every, say, 30 times it accesses BerkeleyDB. > I use 4.2 with p5-BerkeleyDB and no problems for me, but I do nothing > complicated - really just pretend it's 1.85 without bugs! My BerkeleyDB 4.2 with Perl is rock-stable, too. Never a glitch of any kind. > If you don't need the functionality of 4.4 then downgrade back to 4.2 > and keep an eye on the 4.4 and p5-BerkeleyDB ports, and try again in a > few months. I think I'll do that. I believe BerkeleyDB 4.5 has just been released already. I'll wait for it to appear in the ports. I do not actually need the functionality of 4.4. Like you, I just use 4.2 as 1.85 without the bugs. :) Upgrading just seemed like the thing to do. If you look at the Sleepycat bug-list, it seems they fixed a whole lot of them since 4.2; but I cannot say I ever really ran into one. So, I'll wait for 4.5. Not much I can do. Should have been a pretty straightforward upgrade; but it isn't. And analyzing a Perl core dump without symbolic information is pretty useless too. Besides, from my own debug markers I set, it does not core dump in the same place each time. So, it's just that: unstable. Thanks, - Mark