bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: m4-1.4.10 segfault with x86_64 during ./configure when checking whet


From: Mike Frysinger
Subject: Re: m4-1.4.10 segfault with x86_64 during ./configure when checking whether printf supports infinite 'long double' arguments
Date: Fri, 14 Dec 2007 07:15:12 -0500
User-agent: KMail/1.9.7

On Thursday 13 December 2007, Eric Blake wrote:
> According to Gilles Espinasse on 12/12/2007 3:29 PM:
>
> Hi Gilles,
>
> > -- System Information:
> > Debian Release: 4.0
> >   APT prefers stable
> >   APT policy: (500, 'stable')
> > Architecture: amd64 (x86_64)
> > Shell:  /bin/sh linked to /bin/bash
> > Kernel: Linux 2.6.18-5-amd64
> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> >
> > m4-1.4.10 ./configure segfault on amd64
> > conftest[<number vary>]: segfault at 502000 rip 00002b3b28099a7 rsp
> > <number vary> error 6
> >
> > I try this patch with no change
> > http://lists.gnu.org/archive/html/bug-m4/2007-09/msg00007.html
> >
> > On the same machine but with Etch 32b version, it just run with trouble
> > (no test with the patch)
>
> Thanks for the report; I'm adding gnulib, since that would be where the
> fix (if any) should be made.  I need to make an m4 snapshot with a more
> recent gnulib snapshot, to see if we've addressed this in the meantime.
>
> Meanwhile, was configure still coming up with the correct answer, and just
> printing bogus intermediate text, or was it failing to compile because of
> the segv?  Perhaps attaching the complete config.log would be helpful.

on Gentoo, the configure test fails, but otherwise things seem to build/run 
fine.  the little test for infinity handling segfaults.  so if the correct 
answer is obtained by interpreting the segfault the same way ...
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]