Dominique Pelle wrote:

> I observe a bug with the latest Vim-7.2.42 (huge) on Linux x86.
> It's not recently introduced since I can reproduce at least with
> Vim-7.1.314 which comes with Ubuntu-8.10.  It only happens in
> a terminal (gvim does not seem affected).
> 
> Steps to reproduce:
> 
> 1/ start Vim in a terminal (xterm or gnome-terminal) with:   vim -u NONE
> 
> 2/ enter INSERT mode with:    i
> 
> 3/ select (into clipboard) a few lines of text with the mouse from
>    another terminal
> 
> 4/ paste those selected lines with the mouse into Vim (middle click)
> 
> 5/ visual select all text with and reformat with:   <Esc>1GVGgq
> 
> 6/ delete everything with:        :%d
> 
> 7/ enter insert mode again with:    i
> 
> 8/ paste same again text still in clipboard with the mouse (middle click)
> 
> 
> Observe that after pasting test in step 8/, Vim either crashes with:
> 
>     Vim: Caught deadly signal ABRT
>     Vim: preserving files...
> 
> .. or sometimes Vim just misbehaves (hangs or not longer accepts all
> keystrokes for example).  Sometimes the text is not inserted at all
> when pasting the second time at step 8/.
> 
> Running the same test with Valgrind, I see errors 100% of the times
> but so far I did not find how to fix them:
> 
> ==11904== Conditional jump or move depends on uninitialised value(s)
> ==11904==    at 0x47D8548: (within /usr/lib/libXt.so.6.0.0)
> ==11904==    by 0x47D891A: (within /usr/lib/libXt.so.6.0.0)
> ==11904==    by 0x47C23E4: XtDispatchEventToWidget (in 
> /usr/lib/libXt.so.6.0.0)
> ==11904==    by 0x47C2D87: (within /usr/lib/libXt.so.6.0.0)
> ==11904==    by 0x47C1CF6: XtDispatchEvent (in /usr/lib/libXt.so.6.0.0)
> ==11904==    by 0x81415D6: xterm_update (os_unix.c:6513)
> ==11904==    by 0x813F8A1: RealWaitForChar (os_unix.c:4969)
> ==11904==    by 0x813F50E: WaitForChar (os_unix.c:4640)
> ==11904==    by 0x813B53B: mch_inchar (os_unix.c:366)
> ==11904==    by 0x81A4706: ui_inchar (ui.c:193)
> ==11904==    by 0x80D274A: inchar (getchar.c:2959)
> ==11904==    by 0x80D237D: vgetorpeek (getchar.c:2735)
> ==11904==    by 0x80D0919: vgetc (getchar.c:1552)
> ==11904==    by 0x80D0E94: safe_vgetc (getchar.c:1757)
> ==11904==    by 0x806368A: edit (edit.c:711)
> ==11904==    by 0x81233CC: invoke_edit (normal.c:8885)
> ==11904==    by 0x8123372: nv_edit (normal.c:8858)
> ==11904==    by 0x8116C54: normal_cmd (normal.c:1184)
> ==11904==    by 0x80DE8DA: main_loop (main.c:1180)
> ==11904==    by 0x80DE427: main (main.c:939)
> (more errors after that)
> 
> Does anybody else see that bug too?

Perhaps you can trigger it earlier, when it's caused, by setting the
'writedelay' option to some value.

-- 
GOD: That is your purpose Arthur ... the Quest for the Holy Grail ...
                 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui