On Fri, 13 Jul 2012, Lech Lorens wrote:
I have found a 100%-reproducible scenario in which Vim crashes. I work on 2 computers sharing a mouse and a keyboard between them with Synergy 2. One of the computers runs Windows 7 with Cygwin, the other is running Linux. Under Cygwin (no matter whether it is mintty or Cygwin/X with xterm; it doesn't happen with Windows native binaries) I start Vim and in Vim start visual selection. Then with the Cygwin window active I move mouse pointer to the other computer at which point Vim crashes. I tried running Vim from gdb (I think this is the main way of debugging programs under Cygwin) but all I get is a pretty useless stack trace consisting of 4 function names, 3 of which are '??????????????' and the last one is one of Windows system functions (can't remember right now the name). At this point, with no debugger, I can think of debugging the problem by inserting printfs() into Vim and trying to narrow down the suspected part of code. However, this is an extremely tedious job and I hoped that somebody would point out: "Hey, you haven't configured gdb correctly!" or would suggest some other way of dealing with the task.
some other way: it depends on what your objectives and requirements might be in using synergy to display simultaneous editing sessions. you did not state them so replies require rather significant assumptions.
i'm just guessing, here, but the debug job might be complicated by unknown interactions caused by synergy interfering with normal gvim (mouse event control, etc). (i'm assuming you are using gvim since you specify mouse events.)
another way to do simultaneous editing on a linux system and a cygwin (MS) system is to employ one vim session, console vim or gvim, linux or MS platform; just choose one. in that session, split the screen vertically and in one pane open the linux version file, and in the other pane open the MS version file. (one of these files will be local; the other will be remote.) do the editing; do the diffs; do the saves.
i apologize if this overview is too high level or missed your requirements. -- You received this message from the "vim_dev" 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
