On Friday, July 5, 2013 3:56:11 AM UTC+2, char101 wrote: > On Fri, Jul 5, 2013 at 8:55 AM, Charles <p...mail.com> wrote: > > > On Fri, Jul 5, 2013 at 5:43 AM, Christian J. Robinson <h...mail.com> wrote: > > >> > > >> At some point in the last couple of weeks I have noticed that my recent Vim > > >> builds (native Windows 7 binaries built under cygwin) are crashing whenever > > >> my custom 'balloonexpr' is triggered--the balloon shows, then Vim crashes. > > > > > > Hi, > > > > > > If you compile it yourself why note generate a pdb (with /Zi) and then > > > register a postmortem debugger (e.g. windgb) > > > therefore when it crash you can trace the line causing it. > > > > EDIT: Sorry, didn't see that it was build with cygwin.
Hello, I think that the problem is gcc compiler on cygwin. You could try to compile with mingw and gcc-tdm 4.4.0 compiler with the package here: https://code.google.com/p/msysgit/downloads/list and debug with gdb. The 7z file "msysGit-fullinstall-1.8.3-preview20130601.exe" contain all you need (also gdb 6.8), you could manual extract somewhere with 7zip tool. The starting script is msys.bat in the root folder pack directory. In this file (pack msysgit) you have also vim 7.3. To build vim new versions you have Make_ming.mak make file in src vim folder. You can also trace the functions call stack with gdb, to find how vim works: 1.http://dustymabe.com/2012/10/14/trace-function-calls-using-gdb/ 2.See the script http://superadditive.com/software/callgraph.tar.gz in http://blog.superadditive.com/2007/12/01/call-graphs-using-the-gnu-project-debugger/ and http://stackoverflow.com/questions/764382/automate-tracing-in-gdb/1123188#1123188 Hope usefull ! -- -- 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/groups/opt_out.
