From owner-freebsd-stable@FreeBSD.ORG Mon Sep 6 06:37:19 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F15D216A4CE for ; Mon, 6 Sep 2004 06:37:19 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B4D343D58 for ; Mon, 6 Sep 2004 06:37:19 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i866ackG027836; Sun, 5 Sep 2004 23:36:40 -0700 From: kstewart To: freebsd-stable@freebsd.org Date: Sun, 5 Sep 2004 23:37:01 -0700 User-Agent: KMail/1.7 References: <413BC4CD.5090201@hamla.org> <200409061533.39374.doconnor@gsoft.com.au> <413BFFD7.50503@mcsi.pp.ru> In-Reply-To: <413BFFD7.50503@mcsi.pp.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409052337.01634.kstewart@owt.com> cc: Maxim Maximov cc: Sahil Tandon Subject: Re: portsdb -Uu results in coredump X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2004 06:37:20 -0000 On Sunday 05 September 2004 11:12 pm, Maxim Maximov wrote: > Daniel O'Connor wrote: > > On Mon, 6 Sep 2004 15:14, Maxim Maximov wrote: > >>That doesn't help. I tried to entirely delete all /usr/ports, ruby*, > >>portupgrade*, removed /var/db/pkg/pkgdb.db, install those all over again > >>and still get a coredump. > >> > >>SIGSEGV appears in libc.so.4 in __bt_split() and it seems like a real > >>bug in there triggered by ruby_bdb1 and some line in the ports/INDEX. > > Oops, I meant SIGBUS here. > > > Hmm, I am running 6-current (libc.so.5) so perhaps the patch to fix it > > wasn't tested in 4.x? > > What patch are you talking about? I've got coredumps on two my 4.10 > machines and all my 5.x/6 systems didn't get this error, BTW. There is a bug in ruby that shows up as a bus error. Follow the topic on -ports@. There are several ways to alter the INDEX[-5] so that it occurs less frequently. I started using portindexdb because it doesn't error off. I also don't use categories, which it doesn't produce. BTW, if you follow ports-all, you are also supposed to also follow ports@ where this failure has been discussed for several days now. It may seem like a waste of time until something like this pops up. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/