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
> >
> >
