From owner-freebsd-current@FreeBSD.ORG Mon Jul 14 12:40:07 2003 Return-Path: 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 BFD5437B404; Mon, 14 Jul 2003 12:40:07 -0700 (PDT) Received: from phys9911.phys.tue.nl (PHYS9911.phys.tue.nl [131.155.108.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D9B043FBD; Mon, 14 Jul 2003 12:40:06 -0700 (PDT) (envelope-from karelj@phys9911.phys.tue.nl) Received: from phys9911.phys.tue.nl (localhost [127.0.0.1]) by phys9911.phys.tue.nl (8.12.9/8.12.9) with ESMTP id h6EJeFJR048037; Mon, 14 Jul 2003 21:40:15 +0200 (CEST) (envelope-from karelj@phys9911.phys.tue.nl) Received: (from karelj@localhost) by phys9911.phys.tue.nl (8.12.9/8.12.9/Submit) id h6EJeFM2048036; Mon, 14 Jul 2003 21:40:15 +0200 (CEST) Date: Mon, 14 Jul 2003 21:40:15 +0200 From: "Karel J. Bosschaart" To: Andreas Klemm Message-ID: <20030714194015.GA47683@phys9911.phys.tue.nl> References: <200307141842.h6EIgIAq001961@cueball.rtp.FreeBSD.org> <20030714191320.GA13379@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030714191320.GA13379@titan.klemm.apsfilter.org> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: Vim: Caught deadly signal BUS (after -current update with new gcc) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 14 Jul 2003 19:40:08 -0000 On Mon, Jul 14, 2003 at 09:13:20PM +0200, Andreas Klemm wrote: > After -current update (with gcc version 3.3.1) and make world > vim gets bus error ... > > I will rebuild the world and report, if it makes a difference. > Same behaviour on comparable machines after compiler update ?? > > andreas@titan[ttyp2]{1004} ~ vim > Vim: Caught deadly signal BUS > Vim: Finished. > Bus error (core dumped) > andreas@titan[ttyp2]{1005} ~ > I have the same error (however without coredump) on a -current predating the new gcc import. The problem occurred today after a portupgrade to the newest gvim version. I just tried again, and am surprised to find that gvim works now, however on a remote X display. Tomorrow I'll restart the X server on that machine to see if it makes a difference on the local display. Karel.