Stefano Zacchiroli wrote:
> Here's how to reproduce:
>
> ~$ cd
> ~$ ls -al .vimrc
> -rw-r--r-- 1 zack zack 2240 2006-03-27 10:11 .vimrc
> ~$ vim
> ~$ # vim started and exited fine
> ~$ mkdir foo
> ~$ cd foo
> ~/foo$ touch .vimrc
> ~/foo$ vim
>
> Vim: Caught deadly signal SEGV
> Vim: Finished.
> Segmentation fault
>
> According to the attached strace the crash happens just after
> successfully opening the ".vimrc" in the currend working directory.
>
> Executing 'vim -u NONE' does not exhibit the same behaviour, but I
> suspect it is because no file is read at all rather than because the bug
> is specific of my configuration ...
I think this patch should fix it, please verify:
*** option.c~ Mon Apr 10 12:38:55 2006
--- option.c Tue Apr 11 10:11:20 2006
***************
*** 10252,10258 ****
char_u *envname;
{
int opt_idx;
! int dofree;
char_u *p;
if (!option_was_set((char_u *)"cp"))
--- 10252,10258 ----
char_u *envname;
{
int opt_idx;
! int dofree = FALSE;
char_u *p;
if (!option_was_set((char_u *)"cp"))
--
It was recently discovered that research causes cancer in rats.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- 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 ///
