Vim: Caught deadly signal BUS (after -current update with new gcc)

Jeremy Messenger mezz7 at cox.net
Sat Jul 26 12:47:56 PDT 2003


Now, it has been fixed today with the new 6.2.040 patch.

Cheers,
Mezz

On Fri, 18 Jul 2003 13:24:30 -0500, Jeremy Messenger <mezz7 at cox.net> wrote:

> On Fri, 18 Jul 2003 19:36:50 +0200, Matthias Schuendehuette 
> <msch at 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.


More information about the freebsd-current mailing list