| 1 |
On Sat, Aug 10, 2013 at 2:25 PM, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
| 2 |
> Anyone ever seen/can explain these? |
| 3 |
> |
| 4 |
> I had 3 of them, again, apparently during the .configure phase: |
| 5 |
> |
| 6 |
>> 2013-08-10T15:08:36-04:00 myhost kernel: conftest[12233]: segfault at 1 ip |
| 7 |
>> 00007f1fc65e8e47 sp 00007ffff690d6e0 error 4 in |
| 8 |
>> libc-client.so.1.0.0[7f1fc65a8000+102000] |
| 9 |
>> 2013-08-10T15:10:04-04:00 myhost kernel: conftest[23852]: segfault at 1 ip |
| 10 |
>> 00007fb1e5887e47 sp 00007fff7f03f4a0 error 4 in |
| 11 |
>> libc-client.so.1.0.0[7fb1e5847000+102000] |
| 12 |
>> 2013-08-10T15:11:32-04:00 myhost kernel: conftest[3249]: segfault at 1 ip |
| 13 |
>> 00007f0077cd6e47 sp 00007fff70306050 error 4 in |
| 14 |
>> libc-client.so.1.0.0[7f0077c96000+102000] |
| 15 |
|
| 16 |
Yes, I have seen them all the time on multiple boxes. AFAIK this is |
| 17 |
perfectly normal behavior, I think it comes from autoconf trying -- on |
| 18 |
purpose -- to find broken configuration options so it knows what to |
| 19 |
avoid. |
Archives