Loading ...
Sorry, an error occurred while loading the content.

Re: VIM Python interface fails with segfault on Windows

Expand Messages
  • David Halter
    Next one (says the problem has vanished after recompiling VIM with the latest source): VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
    Message 1 of 5 , Jan 5, 2013
    • 0 Attachment
      Next one (says the problem has vanished after recompiling VIM with the
      latest source):

      VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
      MS-Windows 32-bit GUI version with OLE support
      Included patches: 1-46
      Compiled by Bram@KIBAALE
      Big version with GUI. Features included (+) or not (-):
      +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
      +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
      +cmdline_info +comments +conceal +cryptv +cscope +cursorbind
      +cursorshape
      +dialog_con_gui +diff +digraphs -dnd -ebcdic +emacs_tags +eval
      +ex_extra +extra_search +farsi +file_in_path +find_in_path +float
      +folding -footer +gettext/dyn -hangul_input +iconv/dyn +insert_expand
      +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds
      +localmap -lua +menu +mksession +modify_fname +mouse +mouseshape
      +multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg +ole
      -osfiletype +path_extra +perl/dyn +persistent_undo -postscript
      +printer -profile +python/dyn +python3/dyn +quickfix +reltime
      +rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff
      +startuptime
      +statusline -sun_workshop +syntax +tag_binary +tag_old_static
      -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title
      +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra
      +viminfo
      +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim
      -xterm_save +xpm_w32
      system vimrc file: "$VIM\vimrc"
      user vimrc file: "$HOME\_vimrc"
      2nd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
      2nd user exrc file: "$VIM\_exrc"
      system gvimrc file: "$VIM\gvimrc"
      user gvimrc file: "$HOME\_gvimrc"
      2nd user gvimrc file: "$VIM\_gvimrc"
      system menu file: "$VIMRUNTIME\menu.vim"
      Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32
      -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 -DWINVER=0x0400
      -D_WIN32_WINNT=0x0400 /Fo.\ObjGOLYHTR/ /Ox /GL -DNDEBUG /Zl /MT
      -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_GUI_W32
      -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL
      -DDYNAMIC_TCL_DLL=\"tcl83.dll\" -DDYNAMIC_TCL_VER=\"8.3\"
      -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\"
      -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
      -DDYNAMIC_PYTHON3_DLL=\"python31.dll\" -DFEAT_PERL -DDYNAMIC_PERL
      -DDYNAMIC_PERL_DLL=\"perl512.dll\" -DFEAT_RUBY -DDYNAMIC_RUBY
      -DDYNAMIC_RUBY_VER=191 -DDYNAMIC_RUBY_DLL=\"msvcrt-ruby191.dll\"
      -DFEAT_BIG /Fd.\ObjGOLYHTR/ /Zi
      Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS
      oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib
      comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib gdi32.lib
      version.lib winspool.lib comctl32.lib advapi32.lib shell32.lib
      /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib user32.lib
      /nodefaultlib:python27.lib /nodefaultlib:python31.lib
      e:\tcl\lib\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib
      /PDB:gvim.pdb -debug

      2012/12/20 David Fishburn <dfishburn.vim@...>
      >
      > Can you supply your output from :ver.

      --
      You received this message from the "vim_use" 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
    • Tony Mechelynck
      ... This one is long-obsolete 7.3.046 32-bit Windows version from Bram s site. The other was apparently 7.3.000 64-bit Windows version (so from an even more
      Message 2 of 5 , Jan 5, 2013
      • 0 Attachment
        On 05/01/13 13:53, David Halter wrote:
        > Next one (says the problem has vanished after recompiling VIM with the
        > latest source):
        >
        > VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
        > MS-Windows 32-bit GUI version with OLE support
        > Included patches: 1-46
        > Compiled by Bram@KIBAALE

        This one is long-obsolete 7.3.046 32-bit Windows version from Bram's
        site. The other was apparently 7.3.000 64-bit Windows version (so from
        an even more obsolete source). As you can see from the first line, this
        one was compiled on 27 October 2010 and the other two on 16 August 2010.

        For Win32 (or W32 running on W64) I recommend the (currently 7.3.762)
        "Vim without Cream" by Steve Hall, available from
        http://sourceforge.net/projects/cream/files/Vim/

        For a list of the (currently 762) already published bugfixes to Vim 7.3,
        see http://ftp.vim.org/pub/vim/patches/7.3/README


        Best regards,
        Tony.
        --
        The ladies men admire, I've heard,
        Would shudder at a wicked word.
        Their candle gives a single light;
        They'd rather stay at home at night.
        They do not keep awake till three,
        Nor read erotic poetry.
        They never sanction the impure,
        Nor recognize an overture.
        They shrink from powders and from paints ...
        So far, I've had no complaints.
        -- Dorothy Parker

        --
        You received this message from the "vim_use" 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
      Your message has been successfully submitted and would be delivered to recipients shortly.