search

lalitmetkar / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

Trying to use `range()' with very big difference between two arguments results in segmentation fault #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. vim -u NONE -c 'call range(1, 947948399)'

What is the expected output? What do you see instead?
Just E342 error. Instead got «Vim: Caught deadly signal ABRT» with this error.

What version of the product are you using? On what operating system?
vim-7.3.322 (gentoo ~amd64), vim-7.3.346 (mercurial repository, huge features, 
no GUI and CFLAGS=" -O0 -ggdb3 "), x86_64-pc-linux-gnu-gcc version 4.4.5.

Original issue reported on code.google.com by zyx....@gmail.com on 26 Oct 2011 at 4:47

GoogleCodeExporter commented 9 years ago 
Do you get anything else on stderr immediately before the "Caught deadly 
signal" message?

I don't know where this SIGABRT is generated, but that signal is deadly: it can 
be caught, it cannot be blocked; it is usually generated by a library to signal 
a fatal condition from which no recovery is possible, the program can only 
clean up and exit.

See http://en.wikipedia.org/wiki/SIGABRT#Usage

Original comment by antoine....@gmail.com on 26 Oct 2011 at 7:29

GoogleCodeExporter commented 9 years ago 
Fixed by patch 3.7.348.
Patch 3.7.349 fixes a related problem.

Original comment by brammool...@gmail.com on 26 Oct 2011 at 9:42