Date: Mon, 06 Sep 2004 10:12:39 +0400 From: Maxim Maximov <mcsi@mcsi.pp.ru> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: portsdb -Uu results in coredump Message-ID: <413BFFD7.50503@mcsi.pp.ru> In-Reply-To: <200409061533.39374.doconnor@gsoft.com.au> References: <413BC4CD.5090201@hamla.org> <200409061345.43031.doconnor@gsoft.com.au> <413BF944.8070108@mcsi.pp.ru> <200409061533.39374.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Maxim Maximov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?413BFFD7.50503>