Bug 66772 – vim, gvim 6.3-r1 / vim-core 6.3-r2 -> stable

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Ciaran McCreesh 2004-10-08 08:12:47 UTC]

When convenient, please consider stable keywords for the following so that I can remove some messy legacy code in the vim eclass:

    app-editors/vim-6.3-r1      (arm, ia64, ppc64)
    app-editors/gvim-6.3-r1     (amd64, ia64)
    app-editors/vim-core-6.3-r2 (arm, ia64, ppc64)

Thanks

[Comment 1 Tom Gall (RETIRED) 2004-10-09 11:30:56 UTC]

Thanks,  stable on ppc64

[Comment 2 Tom Gall (RETIRED) 2004-10-09 11:34:54 UTC]

oooo wait a second ... I'm getting 

Vim: Caught deadly signal SEGV

Vim: Finished.
Segmentation fault

strike that stable comment!

[Comment 3 Ciaran McCreesh 2004-10-09 11:39:51 UTC]

Is that gvim or vim?

[Comment 4 Tom Gall (RETIRED) 2004-10-09 11:51:19 UTC]

vim ... saw this long ago... looks to be the "same" problem. Basically at application exit the last portion of the stack is corrupt.  vim itself is done, but as glibc unwinds... boom-shakka!

[Comment 5 Ciaran McCreesh 2004-10-09 12:47:22 UTC]

Hm. I'm guessing that this is ppc64 specific. Or at least, I've not seen reports of it on any other arch. Any chance of a gdb backtrace with vim, ncurses and glibc all built with -g and whatever other debugging options your arch needs?

[Comment 6 Simon Stelling (RETIRED) 2004-10-09 13:34:17 UTC]

all stable on amd64

[Comment 7 Akinori Hattori 2004-10-20 07:21:44 UTC]

stable on ia64

[Comment 8 SpanKY 2004-10-30 18:29:14 UTC]

arm done

[Comment 9 Ciaran McCreesh 2004-12-14 12:30:04 UTC]

Marking as FIXED thanks to a later security bug.