On Fri, Apr 14, 2006 at 12:42:53PM +0200, Bram Moolenaar wrote:
>
> Mikolaj Machowski wrote:
>
> > Dnia czwartek, 13 kwietnia 2006 17:19, Bram Moolenaar napisa³:
> > > Benji Fisher wrote:
> > > > I just tried
> > > >
> > > > :!gvim
> > > >
> > > > and all I got was
> > > >
> > > > Vim: Caught deadly signal SEGV
> > > > Vim: Finished.
> > > >
> > > > Command terminated
> > > >
> > > > Press ENTER or type command to continue
> > > >
> > > > I am using vim 7.0d on Linux (FC2). I get the same result running vim
> > > > (in a gnome-terminal) or gvim.
> > >
> > > Works fine for me... Check what program is actually executed, perhaps
> > > in a ":!" shell $PATH is different.
> >
> > Confirming for vim7.0d on Linux Mandriva 2006.0 . $PATH is the same in
> > terminal and inside vim.
> >
> > Problem is in script-space. when both calls are with -u/U NONE I can
> > play with any level. Seem that Benji and me have the same plugins :)
>
> It would be good if you can pinpoint the script that causes a problem.
>
> I first suspected it would have something to do with compiling with
> Python support, thus using threaded libraries, but if -u NONE avoids the
> problem it must be something else.
The problem is neither python nor plugins. This is the default
version compiled on FC2, with Normal features, -python. When I start
gvim with
:!gvim -u ~/.vimrc ~/.gvimrc
there is no segfault and I get the same plugins as if I do
$ gvim
I only get the segfault with
:!gvim
--Benji Fisher
