When dev-db/mysql-5.0.34 is emerged, the following errors are produced in grsec.log and kern.log: Mar 5 15:54:13 localhost grsec: From 10.0.0.15: denied resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 for /var/tmp/portage/dev-db/mysql-5.0.34/work/mysql/dbug/factorial[factorial:151591] uid/euid:0/0 gid/egid:0/0, parent /bin/bash[sh:151584] uid/euid:0/0 gid/egid:0/0 No errors were reported in emerge.log. localhost ~ # equery u mysql [ Searching for packages matching mysql... ] [ Colour Code : set unset ] [ Legend : Left column (U) - USE flags from make.conf ] [ : Right column (I) - USE flags packages was installed with ] [ Found these USE variables for dev-db/mysql-5.0.34 ] U I - - big-tables : Make tables contain up to 1.844E+19 rows - - cluster : Add support for NDB clustering. - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml . - - embedded : Build embedded server (libmysqld) - - extraengine : Add support for alternative storage engines. - - latin1 : Use LATIN1 encoding instead of UTF8. - - max-idx-128 : Raise the max index per table limit from 64 to 128 - - minimal : Install a very minimal build (disables, for example, plugins, fonts, most drivers, non-critical features) - - perl : Adds support/bindings for the Perl language. - - selinux : !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur + + ssl : Adds support for Secure Socket Layer connections - - static : !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically
Created attachment 112350 [details] emerge --info
This is actually expected behavior. 'factorial' is the test program for the debug engine (dbug) that mysql uses. It has 5 testcases that are always used during building, and some of them should never complete. The idea is the test program must crash, and then you can compare it's backtrace against an expected backtrace to see if things are sane. The rlimit_core message is not the usual one that the exit with however - they usually just segfault as designed.
*** Bug 185149 has been marked as a duplicate of this bug. ***
