Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 332595 - vi: buffer overflow attack in function <unknown> - terminated
Summary: vi: buffer overflow attack in function <unknown> - terminated
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Vim Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-13 11:57 UTC by Alessandro Surace
Modified: 2011-04-15 21:39 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,5.49 KB, text/plain)
2010-08-13 12:07 UTC, Alessandro Surace
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alessandro Surace 2010-08-13 11:57:14 UTC
When I try to start vi I get:
*** buffer overflow detected ***: vi - terminated
vi: buffer overflow attack in function <unknown> - terminated


Reproducible: Always

Steps to Reproduce:
1.vi
2.
3.
Comment 1 Alessandro Surace 2010-08-13 12:07:21 UTC
Created attachment 242761 [details]
emerge --info
Comment 2 Alex Legler (RETIRED) archtester gentoo-dev Security 2010-08-17 19:37:58 UTC
Likely just a compilation issue. Reassigning to bug-wranglers
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2010-08-18 15:00:12 UTC
What package is providing this `vi'? Please post the output of `emerge -pqv <cat/pkg>' for that package. Also, provide relevant dmesg output and perhaps see if a backtrace reveals more information.
Comment 4 Alessandro Surace 2010-09-14 15:57:52 UTC
emerge -pqv app-editors/vim
[ebuild   R   ] app-editors/vim-7.0.235  USE="X acl bash-completion gpm nls perl python -cscope -debug -minimal -ruby -vim-pager" 

No further info in dmesg.

How can I backtrace vim?
Comment 5 Alessandro Surace 2010-11-16 11:52:55 UTC
I've rebuild with:
CFLAGS="-march=athlon-tbird -O2 -ggdb" CXXFLAGS="${CFLAGS}" FEATURE="splitdebug" emerge app-editors/vim

And now vim works.

But why does this happen?
Comment 6 Jim Ramsay (lack) (RETIRED) gentoo-dev 2010-12-30 18:48:43 UTC
My guess is that you probably updated to either app-editor/vim-7.2.442 or 7.3.50, both of which have fixed many bugs since version 7.0.235 that you reported you were running earlier.

Please let me know if the following two statements are correct:
 1) You are now running vim-7.2.442 or later
 2) You are no longer seeing the buffer overflow
Comment 7 Alessandro Surace 2011-03-07 09:01:38 UTC
I'm using vim  7.0.235 and I'm no longer seeing the suffer overflow.

The only difference was the USE flag.
Comment 8 Jim Ramsay (lack) (RETIRED) gentoo-dev 2011-04-15 21:39:24 UTC
Perhaps it was simply recompiling the package that fixed the issue then.

Marking as "fixed".