From owner-freebsd-current@FreeBSD.ORG Thu Oct 5 12:21:12 2006 Return-Path: X-Original-To: FreeBSD-CURRENT@FreeBSD.org Delivered-To: FreeBSD-CURRENT@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C95A816A4AB for ; Thu, 5 Oct 2006 12:21:12 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DB4743D6B for ; Thu, 5 Oct 2006 12:21:12 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1515646CCB; Thu, 5 Oct 2006 08:21:12 -0400 (EDT) Date: Thu, 5 Oct 2006 13:21:12 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Dominic Marks In-Reply-To: <20061005130358.3e6984ba.dom@helenmarks.co.uk> Message-ID: <20061005131916.N46123@fledge.watson.org> References: <57153.10.0.2.4.1160049137.squirrel@Rainbow-IT.net> <20061005130358.3e6984ba.dom@helenmarks.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: rainbowit@Rainbow-IT.net, FreeBSD-CURRENT@FreeBSD.org Subject: Re: segmentation fault(s) after upgrading to CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 12:21:12 -0000 On Thu, 5 Oct 2006, Dominic Marks wrote: >> I have just upgraded from FreeBSD_6 STABLE to FreeBSD_7 CURRENT (about >> time I did some testing / early adoption I thought). >> >> [12:49]chrisp@valhalla ~ % uname -a >> FreeBSD valhalla.systems.hq.inty.net 7.0-CURRENT FreeBSD 7.0-CURRENT #1: >> Thu Oct 5 09:38:09 BST 2006 >> chrisp@valhalla.systems.hq.inty.net:/usr/obj/usr/src/sys/VALHALLA i386 >> >> My 'VALHALLA' kernel is a copy of 'GENERIC', but with >> RAID/SCSI/FIREWIRE/ISA_NICs removed. >> >> I have completed the upgrade but now I see many of the programs I run, are >> core dumping... > > Rebuild them. From what I can see they mostly look to be threaded apps. You > might find that doing a fresh install of CURRENT is a better idea in future. > Although I suppose then you wouldn't be testing the upgrade path. Unfortunately, the upgrade path will remain fairly broken with respect to compiled applications outside of the base system until we have a compat6 library set (and possibly more versioning work on libraries?). Some libraries have now been bumped, but not all, and as a result older applications may find themselves linked against libraries with differing ABIs from each other -- i.e., a 6-STABLE libc left over from before your update and a 7-CURRENT libutil (random example), which can result in application crashes. This will presumably get resolved before we get anywhere close to a release, but in the mean time, it is advisable to rebuild all applications when going from an earlier branch to the 7.x branch, or when jumping forward significantly on the branch. Robert N M Watson Computer Laboratory University of Cambridge