Francis (Grizzly) Smit <[email protected]> wrote: > On 02/10/14 04:42, Dominique Pellé wrote: >> >> Francis (Grizzly) Smit <[email protected]> wrote: >>> >>> On 02/10/14 00:57, Francis (Grizzly) Smit wrote: >>>> >>>> I get the following when I try and to open a perl file in gvim >>>> >>>> >>>> >>>> 00:48:37 grizzlysmit@rakbat:~/Projects/perl/heredocs$ gvim hereboy.pl >>>> 00:48:46 grizzlysmit@rakbat:~/Projects/perl/heredocs$ >>>> (gvim:32459): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= >>>> (gint)rarray->len' failed >>>> >>>> ** (gvim:32459): CRITICAL **: unity_gtk_menu_shell_get_item: assertion >>>> '0 <= index && index < items->len' failed >>>> >>>> ** (gvim:32459): CRITICAL **: unity_gtk_menu_item_get_child_shell: >>>> assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed >>>> >>>> ** (gvim:32459): CRITICAL **: unity_gtk_menu_shell_get_item: assertion >>>> '0 <= index && index < items->len' failed >>>> >>>> ** (gvim:32459): CRITICAL **: unity_gtk_menu_item_get_label: assertion >>>> 'UNITY_GTK_IS_MENU_ITEM (item)' failed >>>> >>>> ** (gvim:32459): CRITICAL **: unity_gtk_menu_item_get_icon: assertion >>>> 'UNITY_GTK_IS_MENU_ITEM (item)' failed >>>> Vim: Caught deadly signal SEGV >>>> Vim: Finished. >>>> >>>> >>>> I am running on 32 bit ubuntu 14.04 and I have tried both vim.gnome and >>>> vim.gtk same result I am running the perl-support plugin so it may be >>>> that, mean while does anyone know what causes this crash >>>> >>> Yep it's cased by perl-support.vim when I disable it the problem goes >>> away >> >> >> I just installed perl-support.vim, and I can't reproduce the >> crash with gvim-7.4.463 (GTK2 GUI). Maybe it has been >> fixed since the version of Ubuntu-14.04 (7.4.052). > > > was that on a 32 bit machine or a 64 bit, because this doesn't happen on my > work machine which is ubuntu 14.04 64bit (sorry I forgot to add that > earlier) > See below, all sorted.
I tried on Linux x86_64 and could not reproduce it. >> Does it happen with any Perl file that you try to open? > > > yes > >> Can you try with: gvim -u NONE -U NONE ? > > > yes hmmm we're on to something now it's some thing about my .vimrc or > .gvimrc and the 32 bit thing as it would also bite my work box otherwise > > > hmm gvim -U None is enough so it's my .gvimrc > > this is the line that was doing it: > tmenu Tools.Open NERDTree > should have been: > tmenu Tools.Open\ NERDTree Open NERDTree > > my bad every thing works fine now and come to think of it I don't think I > have NERDTree on my work box nor the menu lines associated with it so that > explains the diff not 32 bit verses 64 bit after all. > > thanks for your help, I never knew about -u NONE and -U NONE before, that > did the trick Glad that you found a workaround, but it's still a bug. Nothing should make Vim crash. I still can't reproduce it. It would be good to check if you can still reproduce it with the latest vim from Mercurial. Dominique -- -- You received this message from the "vim_use" 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 --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
