Segv with gvim 7.d and 7.e

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Segv with gvim 7.d and 7.e

Edward Ash
When I try to run gvim I get a

Vim: Caught deadly signal SEGV

Vim: Finished


I am able to run in console with out a problem.
 

Is there anything I can do to help debug this?

Thanks,

--

Reply | Threaded
Open this post in threaded view
|

Re: Segv with gvim 7.d and 7.e

Benji Fisher
On Sun, Apr 16, 2006 at 04:53:42PM -0600, Edward Ash wrote:

> When I try to run gvim I get a
>
> Vim: Caught deadly signal SEGV
>
> Vim: Finished
>
>
> I am able to run in console with out a problem.
>  
>
> Is there anything I can do to help debug this?

     You could try compiling with the debugging flag set (-DDEBUG) and
then run under gdb.  If you want others to try to reproduce the problem,
please tell us what OS you are running, where you get the vim source (I
recommend ftp://ftp.vim.org/pub/vim/unstable/snapshot/ ) and how you
compile it.

     Make sure you are running the version you think you are running:
use a full path, try

$ vim --version
$ vim -g
$ vim
:gui

and any other variations I may have missed.

HTH --Benji Fisher
Reply | Threaded
Open this post in threaded view
|

Re: Segv with gvim 7.d and 7.e

Edward Ash
I am running on debian sarge.  With the flag prefix=/home/elash1/usr/local
I have set the CFLAG to be -DDEBUG
but when I run gdb it doesn't find the symbols :( any clue?
I noticed if I don't do make install, it works fine.  But otherwise gvim
doesn't work.

I get the following when i do a backtrace within gdb
Program recieved signal sigsegv, segmentaqtion fault.
#0 0x65794f2f in ?? ()
#1 0x400dd491 in XmWidgetGetBaselines () from /usr/lib/libXm.so.2
#2 0x400f24ac in xmOptionLabelGadget () from /usr/lib/libxm.so.2

Eddie


Benji Fisher wrote:

>On Sun, Apr 16, 2006 at 04:53:42PM -0600, Edward Ash wrote:
>  
>
>>When I try to run gvim I get a
>>
>>Vim: Caught deadly signal SEGV
>>
>>Vim: Finished
>>
>>
>>I am able to run in console with out a problem.
>>
>>
>>Is there anything I can do to help debug this?
>>    
>>
>
>     You could try compiling with the debugging flag set (-DDEBUG) and
>then run under gdb.  If you want others to try to reproduce the problem,
>please tell us what OS you are running, where you get the vim source (I
>recommend ftp://ftp.vim.org/pub/vim/unstable/snapshot/ ) and how you
>compile it.
>
>     Make sure you are running the version you think you are running:
>use a full path, try
>
>$ vim --version
>$ vim -g
>$ vim
>:gui
>
>and any other variations I may have missed.
>
>HTH --Benji Fisher
>  
>

Reply | Threaded
Open this post in threaded view
|

Re: Segv with gvim 7.d and 7.e

Benji Fisher
     Did you try the suggestions from my first reply to make sure you
were using the version you thought you were?  If you have multiple
copies of vim installed in various places, it can get confusing.

     Perhaps it would help to run

$ make test
$ make install

and check the second one for error messages.

HTH --Benji Fisher

On Sun, Apr 16, 2006 at 11:35:34PM -0400, Eddie Ash wrote:

> I am running on debian sarge.  With the flag prefix=/home/elash1/usr/local
> I have set the CFLAG to be -DDEBUG
> but when I run gdb it doesn't find the symbols :( any clue?
> I noticed if I don't do make install, it works fine.  But otherwise gvim
> doesn't work.
>
> I get the following when i do a backtrace within gdb
> Program recieved signal sigsegv, segmentaqtion fault.
> #0 0x65794f2f in ?? ()
> #1 0x400dd491 in XmWidgetGetBaselines () from /usr/lib/libXm.so.2
> #2 0x400f24ac in xmOptionLabelGadget () from /usr/lib/libxm.so.2
>
> Eddie
>
>
> Benji Fisher wrote:
>
> >On Sun, Apr 16, 2006 at 04:53:42PM -0600, Edward Ash wrote:
> >
> >
> >>When I try to run gvim I get a
> >>
> >>Vim: Caught deadly signal SEGV
> >>
> >>Vim: Finished
> >>
> >>
> >>I am able to run in console with out a problem.
> >>
> >>
> >>Is there anything I can do to help debug this?
> >>  
> >>
> >
> >    You could try compiling with the debugging flag set (-DDEBUG) and
> >then run under gdb.  If you want others to try to reproduce the problem,
> >please tell us what OS you are running, where you get the vim source (I
> >recommend ftp://ftp.vim.org/pub/vim/unstable/snapshot/ ) and how you
> >compile it.
> >
> >    Make sure you are running the version you think you are running:
> >use a full path, try
> >
> >$ vim --version
> >$ vim -g
> >$ vim
> >:gui
> >
> >and any other variations I may have missed.
> >
> >HTH --Benji Fisher
> >
> >
Reply | Threaded
Open this post in threaded view
|

Re: Segv with gvim 7.d and 7.e

Edward Ash
In reply to this post by Edward Ash
I have tried the make test, and make install.  And both run with out any
errors.
When I do a vim --version i get the following:


>      Did you try the suggestions from my first reply to make sure you
> wIM - Vi IMproved 7.0e BETA (2006 Apr 16, compiled Apr 16 2006 23:19:30)
Compiled by [hidden email]
Normal version with X11-Motif GUI.  Features included (+) or not (-):
-arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
+cryptv -cscope +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic
-emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path
+folding -footer +fork() +gettext -hangul_input -iconv +insert_expand
+jumplist
 -keymap -langmap +libcall +linebreak +lispindent +listcmds +localmap +menu
+mksession +modify_fname +mouse +mouseshape -mouse_dec -mouse_gpm
-mouse_jsbterm -mouse_netterm +mouse_xterm -multi_byte +multi_lang -mzscheme
+netbeans_intg -osfiletype +path_extra -perl +postscript +printer -profile
-python +quickfix -rightleft -ruby +scrollbind +signs +smartindent -sniff
+statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white
-tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands
+vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore
+wildmenu +windows +writebackup +X11 +xfontset +xim +xsmp_interact
+xterm_clipboard -xterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/home/elash1/usr/local//share/vim"
Compilation: /usr/bin/gcc-3.3 -c -I. -Iproto -DHAVE_CONFIG_H
-DFEAT_GUI_MOTIF -DFUNCPROTO=15 -DNARROWPROTO
-I/home/elash1/usr/local/include  -DDEBUG  -I/usr/X11R6/include
Linking: /usr/bin/gcc-3.3  -L/usr/X11R6/lib  
-L/home/elash1/usr/local/lib -L/usr/local/lib -o vim  -lXmu -lXext -lXm
-lncurses
  DEBUG BUILD

After it is installed i can run vim, but not vim -g, gvim , or vim and
then do a :gui with out it seg faulting.
Eddie


>Where using the version you thought you were?  If you have multiple
> copies of vim installed in various places, it can get confusing.
>
>      Perhaps it would help to run
>
> $ make test
> $ make install
>
> and check the second one for error messages.
>
> HTH --Benji Fisher
>
> On Sun, Apr 16, 2006 at 11:35:34PM -0400, Eddie Ash wrote:
> > I am running on debian sarge.  With the flag
prefix=/home/elash1/usr/local
> > I have set the CFLAG to be -DDEBUG
> > but when I run gdb it doesn't find the symbols :( any clue?
> > I noticed if I don't do make install, it works fine.  But otherwise
gvim

> > doesn't work.
> >
> > I get the following when i do a backtrace within gdb
> > Program recieved signal sigsegv, segmentaqtion fault.
> > #0 0x65794f2f in ?? ()
> > #1 0x400dd491 in XmWidgetGetBaselines () from /usr/lib/libXm.so.2
> > #2 0x400f24ac in xmOptionLabelGadget () from /usr/lib/libxm.so.2
> >
> > Eddie
> >
> >
> > Benji Fisher wrote:
> >
> > >On Sun, Apr 16, 2006 at 04:53:42PM -0600, Edward Ash wrote:
> > >
> > >
> > >>When I try to run gvim I get a
> > >>
> > >>Vim: Caught deadly signal SEGV
> > >>
> > >>Vim: Finished
> > >>
> > >>
> > >>I am able to run in console with out a problem.
> > >>
> > >>
> > >>Is there anything I can do to help debug this?
> > >>  
> > >>
> > >
> > >    You could try compiling with the debugging flag set (-DDEBUG) and
> > >then run under gdb.  If you want others to try to reproduce the
problem,

> > >please tell us what OS you are running, where you get the vim source (I
> > >recommend ftp://ftp.vim.org/pub/vim/unstable/snapshot/ ) and how you
> > >compile it.
> > >
> > >    Make sure you are running the version you think you are running:
> > >use a full path, try
> > >
> > >$ vim --version
> > >$ vim -g
> > >$ vim
> > >:gui
> > >
> > >and any other variations I may have missed.
> > >
> > >HTH --Benji Fisher
> > >
> > >
>
>

--

Reply | Threaded
Open this post in threaded view
|

Re: Segv with gvim 7.d and 7.e

Bram Moolenaar

Edward Ash wrote:

> I have tried the make test, and make install.  And both run with out any
> errors.
> When I do a vim --version i get the following:
>
>
> >      Did you try the suggestions from my first reply to make sure you
> > wIM - Vi IMproved 7.0e BETA (2006 Apr 16, compiled Apr 16 2006 23:19:30)
> Compiled by [hidden email]
> Normal version with X11-Motif GUI.  Features included (+) or not (-):
> -arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset +cindent
> +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
> +comments
> +cryptv -cscope +cursorshape +dialog_con_gui +diff +digraphs -dnd -ebcdic
> -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path
> +folding -footer +fork() +gettext -hangul_input -iconv +insert_expand
> +jumplist
>  -keymap -langmap +libcall +linebreak +lispindent +listcmds +localmap +menu
> +mksession +modify_fname +mouse +mouseshape -mouse_dec -mouse_gpm
> -mouse_jsbterm -mouse_netterm +mouse_xterm -multi_byte +multi_lang -mzscheme
> +netbeans_intg -osfiletype +path_extra -perl +postscript +printer -profile
> -python +quickfix -rightleft -ruby +scrollbind +signs +smartindent -sniff
> +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white
> -tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands
> +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore
> +wildmenu +windows +writebackup +X11 +xfontset +xim +xsmp_interact
> +xterm_clipboard -xterm_save
>    system vimrc file: "$VIM/vimrc"
>      user vimrc file: "$HOME/.vimrc"
>       user exrc file: "$HOME/.exrc"
>   system gvimrc file: "$VIM/gvimrc"
>     user gvimrc file: "$HOME/.gvimrc"
>     system menu file: "$VIMRUNTIME/menu.vim"
>   fall-back for $VIM: "/home/elash1/usr/local//share/vim"
> Compilation: /usr/bin/gcc-3.3 -c -I. -Iproto -DHAVE_CONFIG_H
> -DFEAT_GUI_MOTIF -DFUNCPROTO=15 -DNARROWPROTO
> -I/home/elash1/usr/local/include  -DDEBUG  -I/usr/X11R6/include
> Linking: /usr/bin/gcc-3.3  -L/usr/X11R6/lib  
> -L/home/elash1/usr/local/lib -L/usr/local/lib -o vim  -lXmu -lXext -lXm
> -lncurses
>   DEBUG BUILD
>
> After it is installed i can run vim, but not vim -g, gvim , or vim and
> then do a :gui with out it seg faulting.

There are several possible causes:
- GCC 3.3 has bugs.  Try using GCC 3.4.
- Something in the Motif library.  Try using another Motif library.
- If that all fails, try installing GTK.

--
~
~
~
".signature" 4 lines, 50 characters written

 /// Bram Moolenaar -- [hidden email] -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://www.ICCF.nl         ///
Reply | Threaded
Open this post in threaded view
|

Re: Segv with gvim 7.d and 7.e

Edward Ash
In reply to this post by Edward Ash
Looks like it has something to do with the motif library that I used.
I tried changing to a different version of gcc to compile and that
didn't work.  I didn't have another motif library on my machine, but I
did find that I had GTK buried somewhere in a non default location and
used that.  Things started to work then.
Eddie

>
> Edward Ash wrote:
>
> > I have tried the make test, and make install.  And both run with out any
> > errors.
> > When I do a vim --version i get the following:
> >
> >
> > >      Did you try the suggestions from my first reply to make sure you
> > > wIM - Vi IMproved 7.0e BETA (2006 Apr 16, compiled Apr 16 2006
23:19:30)
> > Compiled by [hidden email]
> > Normal version with X11-Motif GUI.  Features included (+) or not (-):
> > -arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset
+cindent
> > +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
> > +comments
> > +cryptv -cscope +cursorshape +dialog_con_gui +diff +digraphs -dnd
-ebcdic
> > -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path
+find_in_path
> > +folding -footer +fork() +gettext -hangul_input -iconv +insert_expand
> > +jumplist
> >  -keymap -langmap +libcall +linebreak +lispindent +listcmds
+localmap +menu
> > +mksession +modify_fname +mouse +mouseshape -mouse_dec -mouse_gpm
> > -mouse_jsbterm -mouse_netterm +mouse_xterm -multi_byte +multi_lang
-mzscheme
> > +netbeans_intg -osfiletype +path_extra -perl +postscript +printer
-profile
> > -python +quickfix -rightleft -ruby +scrollbind +signs +smartindent
-sniff
> > +statusline -sun_workshop +syntax +tag_binary +tag_old_static
-tag_any_white
> > -tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands
> > +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace
+wildignore

> > +wildmenu +windows +writebackup +X11 +xfontset +xim +xsmp_interact
> > +xterm_clipboard -xterm_save
> >    system vimrc file: "$VIM/vimrc"
> >      user vimrc file: "$HOME/.vimrc"
> >       user exrc file: "$HOME/.exrc"
> >   system gvimrc file: "$VIM/gvimrc"
> >     user gvimrc file: "$HOME/.gvimrc"
> >     system menu file: "$VIMRUNTIME/menu.vim"
> >   fall-back for $VIM: "/home/elash1/usr/local//share/vim"
> > Compilation: /usr/bin/gcc-3.3 -c -I. -Iproto -DHAVE_CONFIG_H
> > -DFEAT_GUI_MOTIF -DFUNCPROTO=15 -DNARROWPROTO
> > -I/home/elash1/usr/local/include  -DDEBUG  -I/usr/X11R6/include
> > Linking: /usr/bin/gcc-3.3  -L/usr/X11R6/lib  
> > -L/home/elash1/usr/local/lib -L/usr/local/lib -o vim  -lXmu -lXext -lXm
> > -lncurses
> >   DEBUG BUILD
> >
> > After it is installed i can run vim, but not vim -g, gvim , or vim and
> > then do a :gui with out it seg faulting.
>
> There are several possible causes:
> - GCC 3.3 has bugs.  Try using GCC 3.4.
> - Something in the Motif library.  Try using another Motif library.
> - If that all fails, try installing GTK.
>
> --
> ~
> ~
> ~
> ".signature" 4 lines, 50 characters written
>
>  /// Bram Moolenaar -- [hidden email] -- http://www.Moolenaar.net
  \\\
> ///        sponsor Vim, vote for features --
http://www.Vim.org/sponsor/ \\\
> \\\        download, build and distribute -- http://www.A-A-P.org   
   ///
>  \\\            help me help AIDS victims -- http://www.ICCF.nl     
  ///
>
>

--