Loading ...
Sorry, an error occurred while loading the content.

67842Re: vim 7.3.782 + pathogen 2.2 crashes with segmentation fault

Expand Messages
  • Dave Kuhlman
    Jan 24, 2013
    • 0 Attachment
      Christian Brabandt <cblists <at> 256bit.org> writes:

      >
      > Hi txp!
      >
      > On Do, 24 Jan 2013, txp wrote:
      >
      > > Hello everybody,
      > > I am new to vim (today is my second day) and I ran into a problem which was
      identified as a bug by the extremely
      > helpful people on the #vim irc channel.
      > > This is the situation: when I run vim with the pathogen plugin, which is
      integrated into the vimrc with
      > "call pathogen#infect()" it crashes with the following output:
      > > Vim: Caught deadly signal SEGV
      > > Vim: Finished.
      > > Segmentation fault (core dumped)
      > >
      > > No other plugins are installed.
      > > Vim is in version 7.3.782, pathogen in version 2.2 and my OS is Ubuntu
      64bit 12.10.
      > >
      > > A user in the IRC channel named mgedmin could narrow down the problem based
      on my gdb output which can be
      > found here: http://pastebin.com/xw01MpY2 .
      > > He figured out that it has something to do with --enable-multibyte settings
      for ./configure.
      > > When I build vim in the first place I just ran ./configure with no
      arguments - so I build it again, this time
      > with --enable-multibyte and everything works perfectly, thanks again mgedmin.
      > > So I am happy with this solution but the bug still exists if you have a vim
      version build without --enable-multibyte.
      >
      > Hm, the root cause is 7.3.776 and we need to initialize now reg_buf in
      > case it is not set:
      >
      > diff --git a/src/regexp.c b/src/regexp.c
      > --- a/src/regexp.c
      > +++ b/src/regexp.c
      > @@ -4079,6 +4079,8 @@
      > mch_errmsg("(\n");
      > }
      > #endif
      > + if (reg_buf == NUL || reg_buf == NULL)
      > + reg_buf = curbuf;
      >
      > regards,
      > Christian

      I had the same crash, and had to revert back to a previous revision.

      The above patch fixed this for me.

      - Dave




      --
      --
      You received this message from the "vim_dev" maillist.
      Do not top-post! Type your reply below the text you are replying to.
      For more information, visit http://www.vim.org/maillist.php
    • Show all 5 messages in this topic