vim-6.2.21_1 -- Caught deadly signal BUS

[Karel J. Bosschaart]

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 at .
> 
> 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 at wolfpack:~> vim
> >Vim: Caught deadly signal BUS
> >Vim: Finished.
> >jeff at wolfpack:~>
> >
> >Regards,
> >Jeff
> 
> 
> -- 
> Yu-Shun Wang <yushunwa at isi.edu>           USC Information Sciences Institute

There is a thread about this problem on -current. The workaround:

unsetenv SESSION_MANAGER

Karel.