Date: Fri, 18 Jul 2003 13:24:30 -0500 From: Jeremy Messenger <mezz7@cox.net> To: msch@snafu.de Cc: freebsd-current@freebsd.org Subject: Re: Vim: Caught deadly signal BUS (after -current update with new gcc) Message-ID: <oprsiqq4u98ckrg5@smtp.central.cox.net> In-Reply-To: <200307181936.50526.msch@snafu.de> References: <200307142038.h6EKciQ06885@mailgate5.cinetic.de> <20030715090740.GA77879@phys9911.phys.tue.nl> <20030717061430.GB96381@dragon.nuxi.com> <200307181936.50526.msch@snafu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 Jul 2003 19:36:50 +0200, Matthias Schuendehuette <msch@snafu.de> wrote: > On Thursday 17 July 2003 08:14, David O'Brien wrote: >> I'm willing to commit it as such, but I'd like to hear more people's >> opinion. > > What I found so far: > > - gvim 6.2.21 works under 'twm' > - gvim 6.2.21 works under 'kde 3.1' with SESSION_MANAGER unset > - gvim 6.2.21 works under 'kde 3.1' if running on a remote machine > tunneled through ssh's X11-redirection > > as reported by others: > > - gvim 6.2.21 works without patch 015 > > I looked at patch 015 but I'm not familiar with X11 > SessionManagerProtocol - perhaps some others are able to analyze the > correctness of that patch... I have sent to the vim-dev mailing list yesterday, because I got the same problem. I gave them with info of vim ran under gdb and explained about that 6.2.015 patch cause the crash. The author of VIM uses FreeBSD as well, so hope he will look into this problem. Cheers, Mezz -- bsdforums.org 's moderator, mezz.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?oprsiqq4u98ckrg5>