With the Xcode 2.4 release, the nan_inf_fmt.f90 testcase in 
gfortran.fortran-torture/execute
has begun to segfault on Darwin PPC at both -m32 and -m64. The backtrace from a
segfault
is...

Starting program: /Users/howarth/testdir/nan_inf_fmt/a.out 
Reading symbols for shared libraries .++ done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x3fffe615
0x90101fc8 in strtol_l ()
(gdb) bt
#0  0x90101fc8 in strtol_l ()
#1  0x00255810 in output_float (dtp=0xbfffeb30, f=0x1808c50, value=inf) at
../../../gcc-4.2-20060928/libgfortran/io/write.c:496
#2  0x00256124 in write_float (dtp=0xbfffeb30, f=0x1808c50, source=0xa <Address
0xa out of bounds>, len=-1610603800) at
../../../gcc-4.2-20060928/libgfortran/io/write.c:912
#3  0x002507ec in formatted_transfer (dtp=0xbfffeb30, type=BT_REAL, p=0xa,
kind=4, size=4, nelems=1) at
../../../gcc-4.2-20060928/libgfortran/io/transfer.c:954
#4  0x0024eac8 in *__gfortran_transfer_real (dtp=0x250314, p=0xbfffeaf8,
kind=4) at ../../../gcc-4.2-20060928/libgfortran/io/transfer.c:1237
#5  0x00002a04 in MAIN__ () at nan_inf_fmt.f90:17
#6  0x00003af0 in main (argc=1073735189, argv=0x0) at
../../../gcc-4.2-20060928/libgfortran/fmain.c:18

It has been suggested on the list that this might be due to size mismatch and
that
the new Xcode 2.4 is exposing a latent bug in libgfortran...

http://gcc.gnu.org/ml/fortran/2006-09/msg00103.html


-- 
           Summary: nan_inf_fmt.f90 segfaults on Darwin PPC starting with
                    Xcode 2.4
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libfortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: howarth at nitro dot med dot uc dot edu
 GCC build triplet: powerpc-apple-darwin8
  GCC host triplet: powerpc-apple-darwin8
GCC target triplet: powerpc-apple-darwin8


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29302

Reply via email to