On Sunday, June 17, 2012 9:53:43 PM UTC-5, AndyHancock wrote: > On Jun 17, 10:13 pm, Tony Mechelynck <[email protected]> > wrote: > >On 18/06/12 03:44, AndyHancock wrote: > >>On Jun 17, 8:16 pm, Tony Mechelynck > >><[email protected]>>>> 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 <[email protected]>>>> > >>>> Huge version with GTK2 GUI. Features included (+) or not (-): > >>>> +arabic +autocmd +balloon_eval +browse ++builtin_terms > > <...snip...> > > >>> 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. > > Hmm...I had no idea. It's par for the course in cygwin (or at least, > those installations that make use of X). Using the gvim in Cygwin's X- > windows allows you to bang out and filter entire chunks of text with > unix commands. > > >>> 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! > > Looks like the problem, or something similar, has resurfaced: > > 0 [main] gvim 936 child_info_fork::abort: > C:\cygwin\bin\cyggobject-2.0-0.dll: Loaded to different address: > parent(0x320000) != child(0x3A0000) > > 0 [main] gvim 3824 child_info_fork::abort: > C:\cygwin\bin\cyggobject-2.0-0.dll: Loaded to different address: > parent(0x320000) != child(0x710000) > > Any further suggestions are welcome. I'll wait a bit before posting > in the cygwin forum.
This is not a vim problem, I think this happens a lot with cygwin. Take Tony's sugestion and update your cygwin packages to the latest versions. In particular look up "cygwin rebase". Doing a rebase fixes most of these problems (at least for a while). If you install the windows version and check the option to install the bat files then you can type > gvim.bat -d file1 file1 and have gvim diff the files or whatever you want to do. You can create an alias to make this easier on you: alias g='gvim.bat' Best Regards -- 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
