Date: Mon, 14 Jul 2003 21:40:15 +0200 From: "Karel J. Bosschaart" <K.J.Bosschaart@tue.nl> To: Andreas Klemm <andreas@freebsd.org> Cc: current@freebsd.org Subject: Re: Vim: Caught deadly signal BUS (after -current update with new gcc) Message-ID: <20030714194015.GA47683@phys9911.phys.tue.nl> In-Reply-To: <20030714191320.GA13379@titan.klemm.apsfilter.org> References: <200307141842.h6EIgIAq001961@cueball.rtp.FreeBSD.org> <20030714191320.GA13379@titan.klemm.apsfilter.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030714194015.GA47683>