Re: Error starting gvim and using diff

On 18/06/12 03:44, AndyHancock wrote:
> On Jun 17, 8:16 pm, Tony Mechelynck <antoine.mechely...@gmail.com>
> wrote:
>> On 17/06/12 22:14, AndyHancock wrote:
>>> I'm encountering the following error attempting to start gvim that
>>> is packaged with cygwin. How would I determine if it is a vim or
>>> cygwin problem?
>>>
>>> Error from starting gvim:
>>> -------------------------
>>> $gvim -d /usr/share/vim/vimrc usr/share/vim/vimrc
>>> 2 files to edit
>>> 0 [main] gvim 6092 child_info_fork::abort: C:\cygwin\bin
>>> \cygncursesw-10.dll: Loaded to different address: parent(0x5D0000)
>>> != child(0x380000)
>>> E851: Failed to create a new process for the GUI
>>> Press ENTER or type command to continue
>>>
>>> Error from diffupdate :
>>> ------------------------
>>> 1 [main] gvim 2704 child_info_fork::abort: C:\cygwin\bin
>>> \cygncursesw-10.dll: Loaded to different address: parent(0x5D0000)
>>> != child(0x380000)
>>>
>>> Cannot fork
>>> 0 [main] gvim 3688 child_info_fork::abort: C:\cygwin\bin
>>> \cyggobject-2.0-0.dll: Loaded to different address:
>>> parent(0x320000) ! = child(0x3B0000)
>>>
>>> Cannot fork
>>> E810: Cannot read or write temp files
>>> E97: Cannot create diffs
>>>
>>> Error from diffupdate using vim rather than gvim:
>>> -------------------------------------------------
>>> 1 [main] gvim 5632 child_info_fork::abort: C:\cygwin\bin
>>> \cyggobject-2.0-0.dll: Loaded to different address:
>>> parent(0x320000) ! = child(0x3B0000)
>>>
>>> Cannot fork
>>> E810: Cannot read or write temp files
>>> E97: Cannot create diffs
>>> Cannot fork
>>> 0 [main] gvim 1376 child_info_fork::abort: C:\cygwin\bin
>>> \cygncursesw-10.dll: Loaded to different address: parent(0x380000)
>>> != child(0x5D0000)
>>>
>>> Cannot fork
>>> E98: Cannot read diff output
>>>
>>> Output of "ver":
>>> ----------------
>>> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Feb 21 2012 17:12:21)
>>> Included patches: 1-447
>>> Compiled by Cygwin Ports <cygwin-xf...@cygwin.com>
>>> Huge version with GTK2 GUI. Features included (+) or not (-):
>>> +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
>>> +cindent
>>> +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
>>> +comments
>>> +conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui
>>> +diff
>>> +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search
>>> +farsi
>>> +file_in_path +find_in_path +float +folding -footer +fork()
>>> +gettext
>>> -hangul_input +iconv +insert_expand +jumplist +keymap +langmap
>>> +libcall
>>> +linebreak +lispindent +listcmds +localmap -lua +menu +mksession
>>> +modify_fname
>>> +mouse +mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm
>>> +mouse_netterm
>>> -mouse_sysmouse +mouse_xterm +mouse_urxvt +multi_byte +multi_lang -
>>> mzscheme
>>> +netbeans_intg +path_extra -perl +persistent_undo +postscript
>>> +printer
>>> +profile
>>> -python -python3 +quickfix +reltime +rightleft -ruby +scrollbind
>>> +signs
>>> +smartindent -sniff +startuptime +statusline -sun_workshop +syntax
>>> +tag_binary
>>> +tag_old_static -tag_any_white -tcl +terminfo +termresponse
>>> +textobjects +title
>>> +toolbar +user_commands +vertsplit +virtualedit +visual
>>> +visualextra
>>> +viminfo
>>> +vreplace +wildignore +wildmenu +windows +writebackup +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/share/vim"
>>> Compilation: gcc -g -O2 -pipe -fno-strength-reduce -I/usr/include/
>>> ncursesw -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
>>> -D_REENTRANT -
>>> I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/
>>> atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/
>>> include/pango-1.0 -I/usr/include/gio-unix-2.0/
>>> -I/usr/include/glib-2.0
>>> -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/
>>> freetype2 -I/usr/include/libpng14 -g -O2 -pipe
>>> Linking: gcc -g -O2 -pipe -fno-strength-reduce -I/usr/include/
>>> ncursesw -L/usr/bin -L/usr/lib/ncursesw -o vim.exe
>>> -L/usr/bin -
>>> lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangocairo-1.0 -lXinerama
>>> -lXi -
>>> lXrandr -lXcursor -lXcomposite -lXdamage -lgdk_pixbuf-2.0 -
>>> lpangoft2-1.0 -lgio-2.0 -lXext -lXfixes -lcairo -lpixman-1
>>> -lxcb-shm -
>>> lxcb-render -lXrender -lX11 -lxcb -lXau -lXdmcp -lpng14 -lpango-1.0
>>> -
>>> lm -lbz2 -lfontconfig -lexpat -lfreetype -lz -lgobject-2.0 -lffi -
>>> lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lintl -liconv -lSM -lICE
>>> -
>>> lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -lncurses -lelf -liconv
>>> -
>>> lintl
>>
>> That kind of GUI should be started from within Cygwin X11. If Cygwin
>> X11 is not already running you cannot start a GTK2 GUI.
>
> I could have sworn that I was doing it from a xterm.

Maybe you were, but it didn't jump me in the face. I mentioned it
because running an X11 display on top of the Windows (or Mac OSX) window
manager is a rather rare thing, few people take the trouble.

>
>> The "loaded to different address" error seems to indicate an
>> incompatibility between your Cygwin Vim executable and your Cygwin
>> shared libraries. You might want to update _all_ your installed
>> Cygwin packages to their latest versions.
>
> Done. Problem seems gone for now.
>
>> In general, I recommend to use only the Console version of Cygwin
>> Vim from the Cygwin bash prompt, and/or the native-Windows versions
>> of Console Vim (from the cmd.exe prompt) and of gvim (from cmd.exe
>> prompt and/or from a desktop shortcut).
>
> Agreed...though as I mentioned, I'd swear it was from an xterm. Ah
> well, my fingers are crossed!
>
> Thanks!
>
My pleasure.
Best regards,
Tony.
--
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization?
Gandhi: I think it would be a good idea.

--
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