* Sebastian Siebert <freespacer@gmx.de> [2010-11-21 12:31]:
Am 21.11.2010 11:35, schrieb Guido Berhoerster:
- Sebastian Siebert<freespacer@gmx.de> [2010-11-21 11:02]: [...]
Is there any other solution other than the sledgehammer?
Yes, check out the source code at the specified locations whether there is a potential buffer overflow, the GCC compile time buffer checks are activated for a reason.
Hm, the upstream thinks that is a problem of gcc: http://www.mail-archive.com/vim_dev@googlegroups.com/msg04786.html
vim seems to use some clever optimizations for memory management which break with -D_FORTIFY_SOURCE=2 so in this case it seems justified to replace it with -D_FORTIFY_SOURCE=1 as recommended by upstream. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org