| 1 |
On 2013-08-12 11:24 AM, Paul Hartman <paul.hartman+gentoo@×××××.com> wrote: |
| 2 |
> On Sat, Aug 10, 2013 at 2:25 PM, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
| 3 |
>> Anyone ever seen/can explain these? |
| 4 |
>> |
| 5 |
>> I had 3 of them, again, apparently during the .configure phase: |
| 6 |
>> |
| 7 |
>>> 2013-08-10T15:08:36-04:00 myhost kernel: conftest[12233]: segfault at 1 ip |
| 8 |
>>> 00007f1fc65e8e47 sp 00007ffff690d6e0 error 4 in |
| 9 |
>>> libc-client.so.1.0.0[7f1fc65a8000+102000] |
| 10 |
>>> 2013-08-10T15:10:04-04:00 myhost kernel: conftest[23852]: segfault at 1 ip |
| 11 |
>>> 00007fb1e5887e47 sp 00007fff7f03f4a0 error 4 in |
| 12 |
>>> libc-client.so.1.0.0[7fb1e5847000+102000] |
| 13 |
>>> 2013-08-10T15:11:32-04:00 myhost kernel: conftest[3249]: segfault at 1 ip |
| 14 |
>>> 00007f0077cd6e47 sp 00007fff70306050 error 4 in |
| 15 |
>>> libc-client.so.1.0.0[7f0077c96000+102000] |
| 16 |
|
| 17 |
> Yes, I have seen them all the time on multiple boxes. AFAIK this is |
| 18 |
> perfectly normal behavior, I think it comes from autoconf trying -- on |
| 19 |
> purpose -- to find broken configuration options so it knows what to |
| 20 |
> avoid. |
| 21 |
|
| 22 |
Ok, cool, thanks Paul. It was the first time I'd seen them, so its |
| 23 |
reassuring that I'm not alone... |
| 24 |
|
| 25 |
Would be good to be documented somewhere though... |
| 26 |
|
| 27 |
Thanks again |
Archives