Summary: | dev-util/cvs-1.12.12-r4 fails when compiled with -D_FORTIFY_SOURCE=2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Väth <martin> |
Component: | [OLD] Games | Assignee: | Maintainers for cvs, and cvs related tools (the version control system) [OBSOLETE] <cvs-utils+obsolete> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | atoth, rose, zorry |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 259417 |
Description
Martin Väth
2008-04-20 12:58:09 UTC
compiles fine on today ~x86. so you have problem somewhere else. Thanks. I hadn't expected this, because I thought that autopoint is a rather self-consistent binary. But now I investigated further and found that it is essentially a shell script which calls cvs. It turned out that the culprit was cvs compiled with -D_FORTIFY_SOURCE=2. Probably this means that cvs will fail with hardened. Not sure whether I should close the bug as invalid or whether it should be reassigned to either the cvs or hardened people. You decide... emerge --info, please. confirmed !
this happens approx. from gcc-4.2.0 to gcc-4.3.1 with and cvs compiled with -D_FORTIFY_SOURCE=2 enabled in cflags/cxxflags
if -D_FORTIFY_SOURCE=2 is disabled there's no such problem
>*** %n in writable segment detected ***
>*** %n in writable segment detected ***
>[several hundred times repeated]
this does so much load on the x-server / system, that working isn't possible anymore ...
only killing via magic sysrq key is possible (as last resort)
system:
Portage 2.1.5.4 (default/linux/amd64/2008.0, gcc-4.3.1, glibc-2.8_p20080602-r0, 2.6.26-rc5-zen1.0 x86_64)
=================================================================
System uname: 2.6.26-rc5-zen1.0 x86_64 Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
Timestamp of tree: Tue, 10 Jun 2008 12:16:01 +0000
app-shells/bash: 3.2_p39
dev-java/java-config: 1.3.7, 2.1.6
dev-lang/python: 2.4.4-r9, 2.5.2-r4
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 2.0.0
sys-apps/openrc: 9999
sys-apps/sandbox: 1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.62
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1
sys-devel/binutils: 2.18-r1, 2.18.50.0.4, 2.18.50.0.5, 2.18.50.0.6, 2.18.50.0.7
sys-devel/gcc-config: 1.4.1
sys-devel/libtool: 1.5.26
virtual/os-headers: 2.6.25-r4
ACCEPT_KEYWORDS="amd64 ~amd64"
CBUILD="x86_64-pc-linux-gnu"
+ 01 Feb 2009; Patrick Lauer <patrick@gentoo.org> + +files/cvs-1.12.12-cvs-gnulib-vasnprintf.patch, +cvs-1.12.12-r6.ebuild: + Fixing cvs to work with gcc 4.3.3 which enables FORTIFY_SOURCES. Fixes + #230849. Patch from Bruno Haible <bruno@clisp.org>, thanks to Magnus + Granberg <zorry@ume.nu> for some hints and explanations. *** Bug 230849 has been marked as a duplicate of this bug. *** *** Bug 257465 has been marked as a duplicate of this bug. *** |