I try to use gvim on Windows 7 64 bit, from cygwin. In other words,
this is not Windows-compiled vim, but the one distributed by cygwin:
$ gvim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 18 2010 23:57:10)
When I try to start gvim from the bash command line, I get the following
error message:
1 [main] gvim 4736 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
719 [main] gvim 4736 open_stackdumpfile: Dumping stack trace to
gvim.exe.stackdump
0 [main] gvim 3284 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
612 [main] gvim 3284 open_stackdumpfile: Dumping stack trace to
gvim.exe.stackdump
0 [main] gvim 3364 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
649 [main] gvim 3364 open_stackdumpfile: Dumping stack trace to
gvim.exe.stackdump
0 [main] gvim 5672 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
622 [main] gvim 5672 open_stackdumpfile: Dumping stack trace to
gvim.exe.stackdump
1 [main] gvim 5308 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
723 [main] gvim 5308 open_stackdumpfile: Dumping stack trace to
gvim.exe.stackdump
1 [main] gvim 1220 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
664 [main] gvim 1220 open_stackdumpfile: Dumping stack trace to
gvim.exe.stackdump
3 [main] gvim 5508 fork: child -1 - died waiting for longjmp
before initialization, retry 0, exit code 0x600, errno 11
gvim.exe.stackdump is generated, but the gvim window shows and the
editor seems to be working fine.
I tried with both Xming and with Cygwin X server, with similar results.
Any pointers how to fix this?
--
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
