Christian Brabandt wrote: > Hi Travis! > > On Mi, 12 Aug 2015, Travis Lebsock wrote: > >> I can reproduce the error without any plugins now. >> >> 1. I run the following command in cmd. >> >> gvim -u NONE -N -c:"set beval bexpr='foo'" >> >> 2. Insert some text then hit esc. >> 3. Hover mouse over the text. >> 4. Once foo bubble shows up I click >> 5. Then it crashes > > Hm, I don't know much about Windows Programming. Debugger shows, an > exception is thrown on a WM_LBUTTONDOWN message at gui_win48.c:1951 > after the call to DispatchMessage() > > ,---- > | 1948 if (vk != VK_F10 || check_map(k10, State, FALSE, TRUE, FALSE, > | 1949 NULL, > NULL) == NULL) > | 1950 #endif > | 1951 pDispatchMessage(&msg); > | 1952 } > `---- > > I don't remember Windows Programming much, so I can't say, what the > proper fix would need to be. > > Perhaps someone more knowledgeable than I can analyze this further.
I don't have Windows and I'm also not knowledgeable about Windows. Maybe someone could build Vim for Windows with those tools to chase memory errors: http://www.drmemory.org/ https://code.google.com/p/address-sanitizer/wiki/WindowsPort It may help for this issues and other Windows specific issues. Regards Dominique -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
