Bug 100438 - Vim crashes pasting buffers
Summary: Vim crashes pasting buffers
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: vim (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: All Linux
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-22 13:14 UTC by Stian Skjelstad
Modified: 2007-04-18 16:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-21 14:23:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gdb output (1.38 KB, text/plain)
2003-07-30 14:24 UTC, Stian Skjelstad
no flags Details

Description Stian Skjelstad 2003-07-22 13:14:00 UTC
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):

How reproducible:

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

Additional info:

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
were working.

Comment 1 Karsten Hopp 2003-07-30 13:46:27 UTC
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. 
Then run 
gdb /usr/bin/vim corefile_name, enter 'bt <enter>' and add the output to this bugreport. 

Comment 2 Karsten Hopp 2003-07-30 13:47:16 UTC
and please add the output of "echo $LANG", too 

Comment 3 Stian Skjelstad 2003-07-30 14:24:30 UTC
Created attachment 93258 [details]
gdb output

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

Comment 4 Karsten Hopp 2004-07-21 14:23:38 UTC
this should be fixed in current releases 

Note You need to log in before you can comment on or make changes to this bug.