Something in VIM when it's built with -O3 is corrupting the stack such that when vim is exiting, the application will sigsegv. It's a harmless sigsegv as it turns out as vim is already off the stack and glibc is just cleaning up. I haven't narrowed it down with gdb (as stack corruption is a total PITA to track in this case) but it turns out building VIM with -O2 or less and there aren't any problems. This is specific to VIM too as no other application in the ppc64 universe exhibits this problem. This bug documents a request to catch those that have -O3 set in their CFLAGS and politely turn it down to -O2. Regards, tgall_foo (gentoo-ppc64 team lead)
In vim.eclass, r1.87. Thanks.
thx! closing
