Does gvim functions correctly for any body?

Does gvim functions correctly for any body?

[Rodrigo Medina]

Hi,
Some time ago I have reported a problem with gvim,
it stops because it receives a  SEGV signal when the
OPEN menu-item is selected. I have installed the new
XWin server, but the problem persists.
Does gvim functions correctly for any body?
Thanks in advance for any replay

RM



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: Does gvim functions correctly for any body?

[Jon TURNEY]

On 10/11/2010 02:52, Rodrigo Medina wrote:
> Some time ago I have reported a problem with gvim,
> it stops because it receives a  SEGV signal when the
> OPEN menu-item is selected. I have installed the new
> XWin server, but the problem persists.
> Does gvim functions correctly for any body?

Probably not, it crashes in the same way for me.

This is very like a problem in gvim or one of the GNOME libraries it depends
upon, which can't be fixed in the X server.

Interestingly 'gdb --args gvim -f' doesn't show the problem (so gvim -f might
be a work around).  Attaching to a running gvim with gdb --pid= and then
provoking the crash gives the following backtrace

> (gdb) bt
> #0  0x76bf1ef4 in ?? ()
> #1  0x6ff41795 in g_module_symbol () from /usr/bin/cyggmodule-2.0-0.dll
> #2  0x6ff41d64 in g_module_open () from /usr/bin/cyggmodule-2.0-0.dll
> #3  0x68169cd5 in g_io_modules_scan_all_in_directory () from /usr/bin/cyggio-2.0-0.dll
> #4  0x6e5a3db6 in g_type_module_use () from /usr/bin/cyggobject-2.0-0.dll
> #5  0x68169902 in g_io_modules_scan_all_in_directory () from /usr/bin/cyggio-2.0-0.dll
> #6  0x68169b7e in g_io_modules_scan_all_in_directory () from /usr/bin/cyggio-2.0-0.dll
> #7  0x68180e2b in g_vfs_is_active () from /usr/bin/cyggio-2.0-0.dll
> #8  0x6aa8cdde in g_once_impl () from /usr/bin/cygglib-2.0-0.dll
> #9  0x68180a72 in g_vfs_get_default () from /usr/bin/cyggio-2.0-0.dll
> #10 0x68150893 in g_file_new_for_path () from /usr/bin/cyggio-2.0-0.dll
> #11 0x6af6044f in gtk_recent_manager_get_for_screen () from /usr/bin/cyggtk-x11-2.0-0.dll
> #12 0x6e588cd6 in g_object_freeze_notify () from /usr/bin/cyggobject-2.0-0.dll
> #13 0x6e58a246 in g_object_newv () from /usr/bin/cyggobject-2.0-0.dll
> #14 0x6e58a8f0 in g_object_new () from /usr/bin/cyggobject-2.0-0.dll
> #15 0x6af5ff1b in gtk_recent_manager_new () from /usr/bin/cyggtk-x11-2.0-0.dll
> #16 0x6af5ff3c in gtk_recent_manager_get_default () from /usr/bin/cyggtk-x11-2.0-0.dll
> #17 0x6aebb649 in gtk_file_chooser_button_new () from /usr/bin/cyggtk-x11-2.0-0.dll
> #18 0x6e5a2dd3 in g_type_create_instance () from /usr/bin/cyggobject-2.0-0.dll
> #19 0x6e588bca in g_object_freeze_notify () from /usr/bin/cyggobject-2.0-0.dll
> #20 0x6aebb7c5 in gtk_file_chooser_button_new () from /usr/bin/cyggtk-x11-2.0-0.dll
> #21 0x6e58a246 in g_object_newv () from /usr/bin/cyggobject-2.0-0.dll
> #22 0x6e58a8f0 in g_object_new () from /usr/bin/cyggobject-2.0-0.dll
> #23 0x6aebcf1b in gtk_file_chooser_button_new () from /usr/bin/cyggtk-x11-2.0-0.dll
> #24 0x6aec1873 in gtk_file_chooser_widget_new () from /usr/bin/cyggtk-x11-2.0-0.dll
> #25 0x6e58a246 in g_object_newv () from /usr/bin/cyggobject-2.0-0.dll
> #26 0x6e58a8f0 in g_object_new () from /usr/bin/cyggobject-2.0-0.dll
> #27 0x6aebd565 in gtk_file_chooser_dialog_new () from /usr/bin/cyggtk-x11-2.0-0.dll
> #28 0x6e58a246 in g_object_newv () from /usr/bin/cyggobject-2.0-0.dll
> #29 0x6e58a7a9 in g_object_new_valist () from /usr/bin/cyggobject-2.0-0.dll
> #30 0x6e58a8ce in g_object_new () from /usr/bin/cyggobject-2.0-0.dll
> #31 0x6aebd160 in gtk_file_chooser_dialog_get_type () from /usr/bin/cyggtk-x11-2.0-0.dll
> #32 0x6aebd209 in gtk_file_chooser_dialog_new () from /usr/bin/cyggtk-x11-2.0-0.dll
> #33 0x0055a46a in ?? ()
> #34 0x0057ff09 in ?? ()
> #35 0x0071d000 in ?? ()
> #36 0x00000000 in ?? ()

You might try reverting to previous versions of gvim or GNOME libraries to try
to narrow down where the problem was introduced.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: Does gvim functions correctly for any body?

[Claude Sylvain]

On 09/11/2010 21:52, Rodrigo Medina wrote:

 >
 > Hi,
 > Some time ago I have reported a problem with gvim,
 > it stops because it receives a  SEGV signal when the
 > OPEN menu-item is selected. I have installed the new
 > XWin server, but the problem persists.
 > Does gvim functions correctly for any body?
 > Thanks in advance for any replay
 >

- I have the same problem here, on 2 Cygwin v1.7.x / Windows XP prof.
   computer.

- I reverted back to vim-7.2/gvim-7.2 to avoid that problem.


P.S.: Hope that this problem will be resolved one day.


Claude.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/