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

Valgrind errors when compiled with MzScheme

Expand Messages
  • Bram Moolenaar
    Sergey - When I run the tests under valgrind, while Vim was built with the MzScheme interface, I get a lot of errors. See below. Some may be false warnings,
    Message 1 of 7 , Feb 16, 2013
      Sergey -

      When I run the tests under valgrind, while Vim was built with the
      MzScheme interface, I get a lot of errors. See below.

      Some may be false warnings, but it would be nice if we avoid all errors,
      otherwise we might not spot a real error.


      ==4273== Memcheck, a memory error detector
      ==4273== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
      ==4273== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
      ==4273== Command: ../vim -u unix.vim -U NONE --noplugin -s dotest.in test1.in
      ==4273== Parent PID: 4269
      ==4273==
      ==4273== Invalid write of size 4
      ==4273== at 0x4041801: ???
      ==4273== by 0x4041813: ???
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8272113: _scheme_apply_multi_from_native (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8280977: apply_k (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288273: scheme_top_level_do_worker (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288536: scheme_top_level_do (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82802F3: scheme_find_links_path (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FB38: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826DF7F: define_execute_with_dynamic_state (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826E715: define_values_execute (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826F136: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82FB1E3: body_one_expr (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826E8E6: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== Address 0xbeea1004 is just below the stack ptr. To suppress, use: --workaround-gcc296-bugs=yes
      ==4273==
      ==4273== Invalid write of size 4
      ==4273== at 0x404225B: ???
      ==4273== by 0x4042273: ???
      ==4273== by 0x4041813: ???
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8272113: _scheme_apply_multi_from_native (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8280977: apply_k (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288273: scheme_top_level_do_worker (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288536: scheme_top_level_do (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82802F3: scheme_find_links_path (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FB38: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826DF7F: define_execute_with_dynamic_state (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826E715: define_values_execute (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826F136: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82FB1E3: body_one_expr (in /home/mool/vim/vim73/src/vim)
      ==4273== Address 0xbeea0fc4 is just below the stack ptr. To suppress, use: --workaround-gcc296-bugs=yes
      ==4273==
      ==4273== Invalid write of size 4
      ==4273== at 0x4042AE6: ???
      ==4273== by 0x4042AF2: ???
      ==4273== by 0x4042273: ???
      ==4273== by 0x4041813: ???
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8272113: _scheme_apply_multi_from_native (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8280977: apply_k (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288273: scheme_top_level_do_worker (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288536: scheme_top_level_do (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82802F3: scheme_find_links_path (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FB38: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826DF7F: define_execute_with_dynamic_state (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826E715: define_values_execute (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826F136: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== Address 0xbeea0f84 is just below the stack ptr. To suppress, use: --workaround-gcc296-bugs=yes
      ==4273==
      ==4273== Invalid write of size 4
      ==4273== at 0x4042AE6: ???
      ==4273== by 0x4042AF2: ???
      ==4273== by 0x4042AF2: ???
      ==4273== by 0x4042273: ???
      ==4273== by 0x4041813: ???
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8272113: _scheme_apply_multi_from_native (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8280977: apply_k (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288273: scheme_top_level_do_worker (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288536: scheme_top_level_do (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82802F3: scheme_find_links_path (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FB38: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826DF7F: define_execute_with_dynamic_state (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826E715: define_values_execute (in /home/mool/vim/vim73/src/vim)
      ==4273== Address 0xbeea0f44 is just below the stack ptr. To suppress, use: --workaround-gcc296-bugs=yes
      ==4273==
      ==4273== Invalid write of size 4
      ==4273== at 0x4042AE6: ???
      ==4273== by 0x4042AF2: ???
      ==4273== by 0x4042AF2: ???
      ==4273== by 0x4042AF2: ???
      ==4273== by 0x4042273: ???
      ==4273== by 0x4041813: ???
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8272113: _scheme_apply_multi_from_native (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FF42: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8280977: apply_k (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288273: scheme_top_level_do_worker (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8288536: scheme_top_level_do (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82802F3: scheme_find_links_path (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826FB38: scheme_do_eval (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x826DF7F: define_execute_with_dynamic_state (in /home/mool/vim/vim73/src/vim)
      ==4273== Address 0xbeea0f04 is just below the stack ptr. To suppress, use: --workaround-gcc296-bugs=yes
      ==4273==
      ==4273==
      ==4273== HEAP SUMMARY:
      ==4273== in use at exit: 4,395,894 bytes in 2,695 blocks
      ==4273== total heap usage: 17,979 allocs, 15,284 frees, 5,592,145 bytes allocated
      ==4273==
      ==4273== 24 bytes in 1 blocks are definitely lost in loss record 76 of 344
      ==4273== at 0x402CB7A: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
      ==4273== by 0x84233FA: ofm_malloc (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8423421: ofm_malloc_zero (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8283F6F: make_prim_closure (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x828608C: scheme_make_folding_prim (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8245B38: main (main.c:570)
      ==4273==
      ==4273== 144 bytes in 6 blocks are definitely lost in loss record 242 of 344
      ==4273== at 0x402CB7A: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
      ==4273== by 0x84233FA: ofm_malloc (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8423421: ofm_malloc_zero (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8283F6F: make_prim_closure (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8285F61: scheme_make_prim (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x828915E: do_call_with_prompt (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8308C71: scheme_module_run_finish (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x4040374: ???
      ==4273== by 0x82EE0C7: scheme_module_run_start (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82FA07B: eval_module_body (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82FD9CA: do_start_module.isra.3 (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8304524: start_module (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8306BCB: chain_start_module (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82EE1D7: scheme_module_start_start (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x83043B2: start_module (in /home/mool/vim/vim73/src/vim)
      ==4273==
      ==4273== 144 bytes in 6 blocks are definitely lost in loss record 243 of 344
      ==4273== at 0x402CB7A: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
      ==4273== by 0x84233FA: ofm_malloc (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8423421: ofm_malloc_zero (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8283F6F: make_prim_closure (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8285F61: scheme_make_prim (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x828915E: do_call_with_prompt (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8308C71: scheme_module_run_finish (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x4040374: ???
      ==4273== by 0x82EE0C7: scheme_module_run_start (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82FA07B: eval_module_body (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x82FD9CA: do_start_module.isra.3 (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8304524: start_module (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x83102DD: _dynamic_require.constprop.13 (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8310E2F: scheme_dynamic_require (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8245B38: main (main.c:570)
      ==4273==

      [...]

      ==4273==
      ==4273== 336 bytes in 2 blocks are possibly lost in loss record 280 of 344
      ==4273== at 0x402B629: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
      ==4273== by 0x40112F4: allocate_dtv (dl-tls.c:297)
      ==4273== by 0x4011A9B: _dl_allocate_tls (dl-tls.c:461)
      ==4273== by 0x4ADD470: pthread_create@@GLIBC_2.1 (allocatestack.c:571)
      ==4273== by 0x831AE2B: mz_proc_thread_create_w_stacksize (in /home/mool/vim/vim73/src/vim)
      ==4273==
      ==4273== 404 (328 direct, 76 indirect) bytes in 1 blocks are definitely lost in loss record 284 of 344
      ==4273== at 0x402CB7A: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
      ==4273== by 0x474C1D4: XtMalloc (in /usr/lib/i386-linux-gnu/libXt.so.6.0.0)
      ==4273== by 0x474C474: __XtMalloc (in /usr/lib/i386-linux-gnu/libXt.so.6.0.0)
      ==4273== by 0x4755986: ??? (in /usr/lib/i386-linux-gnu/libXt.so.6.0.0)
      ==4273== by 0x4755A7B: ??? (in /usr/lib/i386-linux-gnu/libXt.so.6.0.0)
      ==4273== by 0x4756757: _XtAppCreateShell (in /usr/lib/i386-linux-gnu/libXt.so.6.0.0)
      ==4273== by 0x4786D40: XtVaAppCreateShell (in /usr/lib/i386-linux-gnu/libXt.so.6.0.0)
      ==4273== by 0x818F466: setup_term_clip (os_unix.c:6639)
      ==4273== by 0x8245EA8: vim_main2 (main.c:761)
      ==4273== by 0x822DEF5: mzscheme_env_main (if_mzsch.c:907)
      ==4273== by 0x8250768: call_with_basic (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8245B38: main (main.c:570)
      ==4273==
      ==4273== 8,192 bytes in 1 blocks are definitely lost in loss record 335 of 344
      ==4273== at 0x402CB7A: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
      ==4273== by 0x8423A17: initialize_signal_handler.isra.59 (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x842AAAD: init_type_tags_worker.isra.63 (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8250838: scheme_set_stack_base (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8245B38: main (main.c:570)
      ==4273==
      ==4273== 8,192 bytes in 1 blocks are definitely lost in loss record 336 of 344
      ==4273== at 0x402CB7A: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
      ==4273== by 0x8423A17: initialize_signal_handler.isra.59 (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x842AAAD: init_type_tags_worker.isra.63 (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x842AE0C: GC_construct_child_gc (in /home/mool/vim/vim73/src/vim)
      ==4273== by 0x8245B38: main (main.c:570)
      ==4273==
      ==4273== LEAK SUMMARY:
      ==4273== definitely lost: 17,064 bytes in 17 blocks
      ==4273== indirectly lost: 196 bytes in 16 blocks
      ==4273== possibly lost: 336 bytes in 2 blocks
      ==4273== still reachable: 4,378,298 bytes in 2,660 blocks
      ==4273== suppressed: 0 bytes in 0 blocks
      ==4273== Reachable blocks (those to which a pointer was found) are not shown.
      ==4273== To see them, rerun with: --leak-check=full --show-reachable=yes
      ==4273==
      ==4273== For counts of detected and suppressed errors, rerun with: -v
      ==4273== ERROR SUMMARY: 15 errors from 13 contexts (suppressed: 0 from 0)

      --
      Computers make very fast, very accurate, mistakes.

      /// Bram Moolenaar -- Bram@... -- 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

      ---
      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 vim_dev+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    • Cesar Romani
      I built vim with racket 5.3.2 (with racket 4.2.5 is not possible) using MinGW on Windows 7, 64-bit and whenever I run, say :mzscheme 5 a ... ViImproved - A
      Message 2 of 7 , Feb 16, 2013
        I built vim with racket 5.3.2 (with racket 4.2.5 is not possible) using
        MinGW on Windows 7, 64-bit and whenever I run, say ':mzscheme 5' a
        windows pops up with the message:

        --------------------
        ViImproved - A Text Editor has stopped working

        A problem caused the program to stop working correctly.
        Windows will close the program and notify you if a solution is available.
        --------------------

        Regards,

        --
        Cesar

        --
        --
        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 vim_dev+unsubscribe@....
        For more options, visit https://groups.google.com/groups/opt_out.
      • Sergey Khorev
        I built vim with racket 5.3.2 (with racket 4.2.5 is not possible) using ... Your command line to build? Works fine with Racket 5.3.3 mingw32-make -f
        Message 3 of 7 , Feb 16, 2013
          I built vim with racket 5.3.2 (with racket 4.2.5 is not possible) using
          MinGW on Windows 7, 64-bit and whenever I run, say ':mzscheme 5' a
          windows pops up with the message:


          Your command line to build?

          Works fine with Racket 5.3.3
          mingw32-make -f Make_ming.mak GUI=yes CSCOPE=yes MZSCHEME=%DEVLIBS%/Racket DYNAMIC_MZSCHEME=no MZSCHEME_VER=3m_8bh220 MZSCHEME_GENERATE_BASE=yes MZSCHEME_PRECISE_GC=yes MZSCHEME_USE_RACKET=yes

          Also could you use another thread?

          --
          --
          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 vim_dev+unsubscribe@....
          For more options, visit https://groups.google.com/groups/opt_out.
           
           
        • Cesar Romani
          ... MZSCHEME_USE_RACKET=yes The problem above only occurs at runtime using racket 5.3.2 with the same command line. With racket 5.3.3 it works fine. Regards,
          Message 4 of 7 , Feb 17, 2013
            On 17/02/2013 01:18 a.m., Sergey Khorev wrote:
            > I built vim with racket 5.3.2 (with racket 4.2.5 is not possible) using
            >
            > MinGW on Windows 7, 64-bit and whenever I run, say ':mzscheme 5' a
            > windows pops up with the message:
            >
            >
            > Your command line to build?
            >
            > Works fine with Racket 5.3.3
            > mingw32-make -f Make_ming.mak GUI=yes CSCOPE=yes
            > MZSCHEME=%DEVLIBS%/Racket DYNAMIC_MZSCHEME=no MZSCHEME_VER=3m_8bh220
            > MZSCHEME_GENERATE_BASE=yes MZSCHEME_PRECISE_GC=yes
            MZSCHEME_USE_RACKET=yes

            The problem above only occurs at runtime using racket 5.3.2 with the
            same command line.
            With racket 5.3.3 it works fine.

            Regards,

            --
            Cesar

            --
            --
            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 vim_dev+unsubscribe@....
            For more options, visit https://groups.google.com/groups/opt_out.
          • Sergey Khorev
            The problem above only occurs at runtime using racket 5.3.2 with the ... Works fine for me. Did you delete mzscheme_base.c and *.o files before building Vim
            Message 5 of 7 , Feb 18, 2013
              The problem above only occurs at runtime using racket 5.3.2 with the
              same command line.
              With racket 5.3.3 it works fine.

              Works fine for me. Did you delete mzscheme_base.c and *.o files before building Vim with another version of MzScheme?

              --
              --
              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 vim_dev+unsubscribe@....
              For more options, visit https://groups.google.com/groups/opt_out.
               
               
            • Bram Moolenaar
              ... I use make reconfig which deletes mzscheme_base.c. -- If all you have is a hammer, everything looks like a nail. When your hammer is C++, everything
              Message 6 of 7 , Feb 18, 2013
                Sergey Khorev wrote:

                > The problem above only occurs at runtime using racket 5.3.2 with the
                > same command line.
                > With racket 5.3.3 it works fine.
                >
                >
                > Works fine for me. Did you delete mzscheme_base.c and *.o files before
                > building Vim with another version of MzScheme?

                I use "make reconfig" which deletes mzscheme_base.c.

                --
                If all you have is a hammer, everything looks like a nail.
                When your hammer is C++, everything begins to look like a thumb.
                -- Steve Hoflich, comp.lang.c++

                /// Bram Moolenaar -- Bram@... -- 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

                ---
                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 vim_dev+unsubscribe@....
                For more options, visit https://groups.google.com/groups/opt_out.
              • Cesar Romani
                ... That was, after deleting mzscheme_base.c it worked. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the
                Message 7 of 7 , Feb 21, 2013
                  On 18/02/2013 10:38 a.m., Sergey Khorev wrote:
                  > The problem above only occurs at runtime using racket 5.3.2 with the
                  >
                  > same command line.
                  > With racket 5.3.3 it works fine.
                  >
                  >
                  > Works fine for me. Did you delete mzscheme_base.c and *.o files before
                  > building Vim with another version of MzScheme?

                  That was, after deleting mzscheme_base.c it worked.

                  --
                  --
                  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 vim_dev+unsubscribe@....
                  For more options, visit https://groups.google.com/groups/opt_out.
                Your message has been successfully submitted and would be delivered to recipients shortly.