Thank you very much for your replies. Both segfaults (readline and gcc) happened during the run of some autoconf scripts. For readline it happened in src_configure step. However, in case of gcc it happened by the end of src_compile step when running some autoconf script right after the gcc stage 2 and 3 were compared.
Ok, then I will not worry about these messages. Regards, Balint On Tue, April 23, 2013 22:51, Mr G wrote: > Ive seen this also. Everything seems to work fine. I believe I seen it on > 386 with XT also. > > B G > On Apr 23, 2013 2:45 PM, "Luis Ressel" <[email protected]> wrote: > >> Haven't looked into this specific message, but I guess you shouldn't >> worry about it too much. The denials (ulimits) would also occur on >> gentoo-sources (or every other kernel, for that matter), they just >> wouldn't be recorded. And most probably it's the same with the >> segfault. It happens always, you just don't get a message about it on >> non-hardened kernels. You might want to check out if the segfaults >> happen during the the run of an autoconf script or something similar >> which just checks for some exotic system configuration. I've also >> encountered more than one mysterious segfault...
