55570Re: Bug on FreeBSD 5.4
- Dec 3, 2009On 03/12/09 21:16, JD wrote:
> On Dec 3, 4:26 am, Tony Mechelynck<antoine.mechely...@...>No perl and no ruby. If the ftplugins assume that you got the interfaces
>> On 03/12/09 08:03, JD wrote:
>>> On Dec 3, 1:46 am, Tony Mechelynck<antoine.mechely...@...>
>>>> On 03/12/09 05:20, JD wrote:
>>>>> Vim is hardlocking for me on every single run on my FreeBSD 5.4
>>>>> system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken.
>>>>> It appears to compile fine, but on run, it fails to respond to any
>>>>> keystrokes and eats nearly 100% of my CPU till I send it a
>>>>> SIGKILL...Please help. :)
>>>> Does it always hang, even if you start it as
>>>> vim -N -u NONE
>>>> gvim -N -u NONE
>>>> Best regards,
>>>> Re graphics: A picture is worth 10K words -- but only those to describe
>>>> the picture. Hardly any sets of 10K words can be adequately described
>>>> with pictures.
>>> It appears to work fine launching vim with -N -u NONE, when not
>>> launching with '-N -u NONE', i've so far narrowed it down to 2
>>> filetypes. I tried opening a ruby script, a perl script, a python
>>> script and a C++ source file and the only ones that failed and caused
>>> vim to lock were the ruby script and the perl script. I moved the
>>> affected scripts to a different directory (same dir as the C++ source)
>>> and the issue still occurred and as far as i can tell, the permissions
>>> on all 4 files are the same.
>> Hm. This is a little bit out of my depth, but I suggest the following:
>> - does the hang still happen when editing these filetypes in a Vim
>> started with
>> vim -u /usr/local/share/vim/vim72/vimrc_example.vim
>> ? (assuming that that's your $VIMRUNTIME directory -- it should be,
>> unless you changed the default at compile-time or unless you're using an
>> obsolete version older than 7.2.0)
>> - did you compile with +ruby or -ruby, +perl or -perl ? (see the output
>> of ":version" -- if you enable them at configure-time, but configure
>> doesn't find the right files, it will turn them off)
>> - do you have any "custom" scripts (scripts not distributed with Vim)
>> which apply to Perl and/or Ruby? (and which ones if you do?)
>> - what are the dates mentioned near the top of the _text_ of the
>> following scripts? I'm mentioning what I see in mine
>> $VIMRUNTIME/filetype.vim 2009 Sep 18
>> $VIMRUNTIME/ftplugin/perl.vim 20 Jan 2009
>> $VIMRUNTIME/ftplugin/ruby.vim 2008/06/29 04:18:43
>> $VIMRUNTIME/syntax/perl.vim 2006 November 23
>> $VIMRUNTIME/syntax/ruby.vim 2008/06/29 04:33:41
>> $VIMRUNTIME/indent/perl.vim 2005 Sep 07
>> $VIMRUNTIME/indent/ruby.vim 2008/06/29 04:18:43
>> - does the hang happen if you do
>> (a) syntax off
>> (b) filetype indent off
>> (c) filetype plugin off
>> before editing the files? (try them one at a time, and turn them back on
>> Best regards,
>> The law will never make men free; it is men who have got to make the
>> law free.
>> -- Henry David Thoreau
> Here's the output of version:
> VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Dec 3 2009 06:48:09)
> Included patches: 1-315
> Compiled by jdhore@...
> Big version with GTK GUI. Features included (+) or not (-):
> +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
> +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
> +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -
> +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path
> +float +folding -footer +fork() +gettext -hangul_input +iconv
> +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds
> +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec -
> -mouse_jsbterm +mouse_netterm +mouse_sysmouse +mouse_xterm
> +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra -perl
> +printer -profile -python +quickfix +reltime +rightleft -ruby
> +signs +smartindent -sniff +startuptime +statusline -sun_workshop
> +tag_binary +tag_old_static -tag_any_white -tcl +terminfo
> +textobjects +title +toolbar +user_commands +vertsplit +virtualedit
> +visualextra +viminfo +vreplace +wildignore +wildmenu +windows
> +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: "/usr/local/share/vim"
> Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/
> local/include/gtk12 -I/usr/local/include/glib12 -I/usr/local/include -
> I/usr/X11R6/include -I/usr/local/include -g
> Linking: gcc -L/usr/local/lib -o vim -L/usr/local/lib -L/usr/X11R6/
> lib -lgtk-12 -lgdk-12 -Wl,-E -lgmodule-12 -lglib-12 -lintl -lXi -lXext
> -lXt -lm -lncurses -lintl
if you edit the files, you're stuck. The versions I have don't seem to,
though (ftplugin/perl.vim doesn't call the Vim/Perl interface and
ftplugin/ruby.vim properly tests <if has("ruby")> AFAICT. However, there
could be something I didn't notice.
>Sorry, you misunderstood me. I didn't want the modification dates as set
> dates of those files:
> $VIMRUNTIME/filetype.vim 2009 Dec 3 06:48 (UTC/GMT)
> $VIMRUNTIME/ftplugin/perl.vim 2009 Dec 3 06:48
> $VIMRUNTIME/ftplugin/ruby.vim 2009 Dec 3 06:48
> $VIMRUNTIME/syntax/perl.vim 2009 Dec 3 06:48
> $VIMRUNTIME/syntax/ruby.vim 2009 Dec 3 06:48
> $VIMRUNTIME/indent/perl.vim 2009 Dec 3 06:48
> $VIMRUNTIME/indent/ruby.vim 2009 Dec 3 06:48
out in the directory (which are the dates you installed these files) but
the dates mentioned in the _text_ of the files, somewhere near the top,
which are the "Last change" dates written there by whoever edited them.
>You also have the filetype-plugins distributed with Vim, namely
> The only custom scripts i have installed are: SyntaxAttr, BufExplorer,
> securemodelines and taglist none of which (i believe) are ruby/perl
> When i ran with 'vim -u /usr/local/share/vim/vim72/vimrc_example.vim',
> it still hung. Also, gdb hasn't given me a useful backtrace.
> With syntax, indent and plugin all off, the file(s) open fine.With
> just syntax on, the file(s) open fine. With syntax and indent on, the
> file(s) open fine. When i enabled plugin, that's when vim started
> hanging. I removed all 4 plugins from .vim/plugin (the only place i
> have any plugins) and with 'filetype plugin on', it still hung.
$VIMRUNTIME/ftplugin/perl.vim and $VIMRUNTIME/ftplugin/ruby.vim. These
are enabled/disabled by "filetype plugin on/off".
"The identical is equal to itself, since it is different."
-- Franco Spisani
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
- << Previous post in topic Next post in topic >>