From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020827
Description of problem:
Pasting a buffer over a marked text, crashes vim (and you must send it a signal
9 to kill it). If you send a regular kill signals, it dumps stuff to console,
but don't die.
[root@pluto libpackage]# vim extract.c
Vim: Caught deadly signal SEGV
Vim: preserving files...
Vim: Double signal, exiting
Version-Release number of selected component (if applicable):
Steps to Reproduce:
* Open a file full of stuff
* Mark text (visual mode) and yank it
* Mark some new text, and press "p" (paste) while the text is marked
Actual Results: It crashes
Expected Results: Replace the selected area with the text in the buffer
I have testes this on a three up to date redhat 7.3 boxes. (One vanilla, one
rebuilt repaired one, and one upgraded from 7.1 where vim just froze the screen
and not showing any SEGV text at all)
Reopen file and restoring swap-file results in some random junk at the place you
Please set the corefile size to unlimited (maybe only allowed for root) with ulimit -c 9999999
and try to reproduce the bug. This will create a core-file in the current directory.
gdb /usr/bin/vim corefile_name, enter 'bt <enter>' and add the output to this bugreport.
and please add the output of "echo $LANG", too
Created attachment 93258 [details]
vim doesn't generate core files since it has a SIGSEGV handler that works (but
hangs), but vim can be run directly from gdb (opt. with remote tty). The $LANG
is set to en_US.
The crash only occures if the buffer you want to overwrite contains minimum one
this should be fixed in current releases