Raymond Ko wrote: [...]
> > > Here is where it crashed for me: > > > http://i.imgur.com/rkiaz.png > > > > Thanks, that is very useful. > > > > > Searching for the "length" variable, I do not see it initialized > > > anywhere prior to use by SvPV(). Maybe this is triggering an out of > > > bound read/write somewhere? > > > > "length" is set by the macro. Searching a bit suggested that PL_errgv > > might be NULL. And indeed, skipping the SvPV macro when PL_errgv is > > NULL solves the crash. > > > > However, it appears errors in perl_eval_sv() are now not reported, thus > > it's a workaround, not a solution. > > > > Perhaps there is a mismatch in the installed Perl version and the Vim > > compilation? > > Although I am not an expert at Perl bindings by any means, I just > noticed this interesting fact: Compiling with the latest MinGW from > http://sourceforge.net/projects/mingwbuilds/files/windows-host/ > (i686-mingw-w64-gcc-4.7.1-release-c,c++,fortran-sjlj-rev2.7z) does not > make Perl bindings crash (tested with :perl VIM::Msg("hello")). > > If the dependencies of executables produced by MinGW is similar to > MSVC 2008 Express, then it might be a possible option to produce > official Windows binaries with MinGW instead. The Make_ming.mak file > should be tweaked to use "-O2 -flto -fwhole-program" as optimization > flags (-O3 produced a miscompiled VIM binary that crashes). I have had problems with MingW in the past. I prefer to build with MSVC. Sticking with one compiler usually works best, other compilers have other problems... > The only tradeoff of using MinGW, at least in my experience, is that > you can't use the JIT Debugging as mentioned in my previous post, > making post-mortem debugging and stacktraces impossible, and that > there is no profiling tools available for MinGW like in MSVC. This > shouldn't really affect end users though. In fact, if you want to use > the Command-T plugin for VIM on Windows, you have to use MinGW as it > has a C extension for the Ruby bindings. My guess is that Ruby C > bindings are in C99, which MSVC does not support, and as a result it > does not compile. Of course this assumes you are using Ruby from > http://rubyinstaller.org/ which includes a DevKit to allow you compile > C extensions. > > Based on some random googling, the whole issue seems to be related to > this bug, which is supposedly fixed?: > https://rt.perl.org/rt3/Public/Bug/Display.html?id=20772 If it is already fixed, then in what version? And where is it broken? I did install the latest version of Perl. I prefer the Vim code to work with most Perl versions anyway. -- hundred-and-one symptoms of being an internet addict: 216. Your pet rock leaves home. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- 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
