From owner-freebsd-current@FreeBSD.ORG Mon Jul 17 09:57:41 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 8B0B716A4DA for ; Mon, 17 Jul 2006 09:57:41 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17C1543D46 for ; Mon, 17 Jul 2006 09:57:40 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k6H9vdnV012037 for ; Mon, 17 Jul 2006 05:57:39 -0400 (EDT) Date: Mon, 17 Jul 2006 05:57:39 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: freebsd-current@freebsd.org In-Reply-To: <86ejwkrh83.fsf@student.uni-magdeburg.de> Message-ID: References: <44BADEC8.5030807@fastmail.fm> <86ejwkrh83.fsf@student.uni-magdeburg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Subject: Re: Firefox on -current dumps core. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2006 09:57:41 -0000 On Mon, 17 Jul 2006, Wolfram Fenske wrote: > Patrick Bowen writes: > >> Hello. >> >> I recently upgraded a Gateway MX6121 from 6.1 stable to -current, >> following the canonical procedure in /usr/src/UPDATING, and now >> whenever I try to start firefox, it dumps a core file (segmentation >> fault). Firefox was compiled from source under 6.1. >> >> Should I have upgraded from 6.1 to -current, and /then/ start adding >> ports, or does that matter? > > When I upgraded about two weeks ago, a lot of programs dumped core. > Rebuilding fixed that. I didn't have these problems when I upgraded > before, not even from 6.0 to 7.0-current, just this last time. Because there are libraries whose version have not been bumped yet in 7.0. -- DE