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