On Wed, 20 Jun 2012 21:22:13 -0700 Jonathon Merz <[email protected]> wrote:
> Hi, > > I've recently discovered an intermittently reproducible crash in GVim > on Windows 7, even using 7.3.566 built today. It's may be a bit hard > for somebody else to debug since it's not reproducible every time and > it's dependent on something in my .vimrc and/or .vim directory (I can > never make it happen running with '-u NONE -U NONE'). > > At any rate, I've built using the Cygwin cross-compiler for mingw32 > using the Make_ming.mak makefile, and I'm not quite sure how to get > GVim for Windows running under a debugger with that (I don't have > access to Visual Studio unfortunately). If anyone has any suggestions > on how to go about looking into this, I'd much appreciate it. There's gdb for Windows: https://www.google.com/search?hl=en&source=hp&q=gdb%20windows&aq=f&aqi=&aql=&oq= I think you can install it from the cygwin’s package repository. Regards, Shlomi Fish > > If anyone is interested in further details, the crash happens maybe > 30-40% of the time when opening a binary file AutoHotKey.aps from the > AutoHotKey project (I originally opened the file because it matched a > string I was looking for and didn't realize it was a binary, and Vim > crashed and I became a little obsessed :) The file is available from: > > https://github.com/AutoHotkey/AutoHotkey/blob/87d18441dd50e3436cdd868702e20d45827ca3cc/Source/resources/AutoHotkey.aps > > I suspect that it has something to do with syntax coloring because: > (1) the file is mis-recognized as XML (... there /is/ a plain-text > XML blob near the beginning of the file with the <?xml...> tag on the > first line of the file after long string of non-printable characters), > (2) there are some very long lines in the file (one ~19000 characters). > (3) when the crash happens, the text in the GVim window has usually > not finished drawing (but not always). > > This isn't a real big problem in my book because I don't actually need > to edit the file and a binary file with very long lines that gets > mistaken for XML is probably a bit of a niche case, but if I can track > it down well enough to fix it or provide somebody else with the info > to fix it I'm happy to. > > Thanks for any advice, > > Jonathon > -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ Parody of "The Fountainhead" - http://shlom.in/towtf My Commodore 64 is suffering from slowness and insufficiency of memory, and its display device is grievously short of pixels. Can anybody help? — Omer Zak Please reply to list if it's a mailing list post - http://shlom.in/reply . -- 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
