(or the appropriate flags passed to it) 13:22 < swtaylor> so why is the other system of mine reporting everything including those two as killed 13:23 < pipacs> that's weird, it should not 13:23 < pipacs> could be a paxtest bug 13:23 < pipacs> what's the gcc version on these two machines? 13:24 < swtaylor> glibc: GNU C Library stable release version 2.3.2, by Roland McGrath et al. 13:24 < swtaylor> glibc: Compiled by GNU CC version 3.3.2 20031201 (Gentoo Linux 3.3.2-r4, propolice). 13:24 < swtaylor> gcc: gcc version 3.3.2 20031201 (Gentoo Linux 3.3.2-r4, propolice) 13:24 < swtaylor> ld: GNU ld version 2.14.90.0.7 20031029 13:24 < swtaylor> all of my machines are the current ~x86, except for having rolled back glibc to the -r9 13:25 < pipacs> but same gcc on both? 13:25 < swtaylor> yes. 13:26 < pipacs> ok, can you send me the rettofunc[12] executables from the machine where they get killed? 13:26 < swtaylor> paxtest on the one reporting everything killed was possibly compiled while an earlier hcc profile was in there, and was compiled while the snapshot glibc was in there 13:26 < pipacs> ah, actually propolice might be causing a problem then 13:26 < pipacs> i mean, it will catch the error and you will see the killed message then 13:26 < swtaylor> should i recompile without hcc now 13:27 < pipacs> yes please 13:27 < pipacs> if those two tests still get killed, i'll need those two files 13:28 < swtaylor> ok this time they report as being vulnerable 13:29 < swtaylor> i guess we should force a few more options during the build of paxtest 13:29 < pipacs> ok, so it was propolice most likely 13:29 < pipacs> which makefile did you use? 13:29 < swtaylor> just emerge paxtest 13:29 < pipacs> gentoo-hardened? 13:29 < pipacs> oh, then report that to solar ;)
Please retry this with the -r1
Scott talk to me. I want to close this.
That seems to have done the trick.
