Date: Tue, 15 Jul 2003 09:59:13 +0200 From: "Karel J. Bosschaart" <K.J.Bosschaart@tue.nl> To: Yu-Shun Wang <yushunwa@ISI.EDU> Cc: Jeff Walters <jeff@walters.name> Subject: Re: vim-6.2.21_1 -- Caught deadly signal BUS Message-ID: <20030715075913.GA68825@phys9911.phys.tue.nl> In-Reply-To: <3F134635.2020807@isi.edu> References: <3F134635.2020807@isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 15, 2003 at 02:09:25AM +0200, Yu-Shun Wang wrote: > Hi, Jeff, > > Yeah, that happens to me too after portupgrade. The annoying thing is, > if I su and run "vim -g", it actually works. For some reason, I just > couldn't start gvim or vim -g as myself. > > Please CC me because I am not subscribed to freebsd-ports@. > > Regards, > > yushun. > > >I don't see any other comments in the list archive nor recent updates in > >CVS so I'll ask, is it just me who's getting a bus signal error with the > >latest vim+ruby-6.2.21_1 update? vim-lite built successfully, but on vim > >and vim+ruby here's the error text: > > > >jeff@wolfpack:~> vim > >Vim: Caught deadly signal BUS > >Vim: Finished. > >jeff@wolfpack:~> > > > >Regards, > >Jeff > > > -- > Yu-Shun Wang <yushunwa@isi.edu> USC Information Sciences Institute There is a thread about this problem on -current. The workaround: unsetenv SESSION_MANAGER Karel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715075913.GA68825>