Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
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 <[EMAIL PROTECTED]> wrote: On Fri, 18 Jul 2003 19:36:50 +0200, Matthias Schuendehuette <[EMAIL PROTECTED]> 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
On Fri, 18 Jul 2003 19:36:50 +0200, Matthias Schuendehuette <[EMAIL PROTECTED]> 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
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... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
On Tue, Jul 15, 2003 at 11:07:40AM +0200, Karel J. Bosschaart wrote: > FWIW, the new behaviour of vim is caused by patch 6.2.015. I added 015 > to BADPATCHES in the ports Makefile and reinstalled. gvim works as usual > now. I'm willing to commit it as such, but I'd like to hear more people's opinion. -- -- David ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
On Mon, Jul 14, 2003 at 10:46:43PM +0200, Andreas Klemm wrote: > On Mon, Jul 14, 2003 at 10:38:44PM +0200, Thorsten Greiner wrote: > > > > You can work around this by unsetting SESSION_MANAGER in your > > > > environment. I have no idea what the root cause is... > > > > > > Where can I get rid of this variable ? I see no easy way. > > > Currently I use gvim as default text editor within KDE > > > environment ... > > > > > > In an xterm or such I could disable it, but how for KDE ?? > > > > As far as I understand it, this variable is set by the session management of the > > respective desktop (KDE in your case, GNOME in mine). Maybe you can workaround the > > problem by using a small shell script which unsets SESSION_MANAGER and than calls > > gvim? > > Yes I will try to write a wrapper script around gvim. > This way ... > > mv vim vim.bin > cat > vim <<- EOF > unset SESSION_MANAGER > vim.bin > EOF > chmod 555 vim > FWIW, the new behaviour of vim is caused by patch 6.2.015. I added 015 to BADPATCHES in the ports Makefile and reinstalled. gvim works as usual now. Karel. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
On Mon, Jul 14, 2003 at 10:38:44PM +0200, Thorsten Greiner wrote: > > > You can work around this by unsetting SESSION_MANAGER in your > > > environment. I have no idea what the root cause is... > > > > Where can I get rid of this variable ? I see no easy way. > > Currently I use gvim as default text editor within KDE > > environment ... > > > > In an xterm or such I could disable it, but how for KDE ?? > > As far as I understand it, this variable is set by the session management of the > respective desktop (KDE in your case, GNOME in mine). Maybe you can workaround the > problem by using a small shell script which unsets SESSION_MANAGER and than calls > gvim? Yes I will try to write a wrapper script around gvim. This way ... mv vim vim.bin cat > vim <<- EOF unset SESSION_MANAGER vim.bin EOF chmod 555 vim Andreas /// -- Andreas Klemm - Powered by FreeBSD 4.8-STABLE Need a magic printfilter today ? -> http://www.apsfilter.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
> > You can work around this by unsetting SESSION_MANAGER in your > > environment. I have no idea what the root cause is... > > Where can I get rid of this variable ? I see no easy way. > Currently I use gvim as default text editor within KDE > environment ... > > In an xterm or such I could disable it, but how for KDE ?? As far as I understand it, this variable is set by the session management of the respective desktop (KDE in your case, GNOME in mine). Maybe you can workaround the problem by using a small shell script which unsets SESSION_MANAGER and than calls gvim? Regards -Thorsten Nur bei WEB.DE Testsieger FreeMail testen und damit 1 qm Regenwald schuetzen. Jetzt anmelden und mithelfen! http://user.web.de/Regenwald ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
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 ?? > > [EMAIL PROTECTED] ~ vim > Vim: Caught deadly signal BUS > Vim: Finished. > Bus error (core dumped) > [EMAIL PROTECTED] ~ > 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"