Wednesday, October 1, 2014

Re: gvim crashing on perl files

Hi Francis!

On Do, 02 Okt 2014, Francis (Grizzly) Smit 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

Can you get a backtrace?

Best,
Christian
--
Der Mann wird es wird bringen, denn er glaubt, was er sagt.
-- Honoré Graf von Mirabeau über Robespierre

--
--
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 vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment