very strange things happen to me!

[Martin Kahlert]

(This mail was sent to the linux.system newsgroup, too.)

Hi,
i have a very strange problem after jumping to linux-2.2.10 (2.2.5
produces the same behaviour):
I have a dual PPRO system.

This fortran prog:

      WRITE(*,*) 'HALLO FORTRAN'
      END

and the tcsh script
while 1
   g77 -o t t.f ; ./t
end

produces an irregular column of
HALLO FORTRAN and Segmentation fault strings.
The executables, which produce SegFaults produce them every time.
The running ones run every time.

I thought it could be my binutils, but 2.9.1.0.22 and 2.9.1.0.25
produce the same behaviour.
My g77 is from egcs-1.1.2 and the newest snapshot for the upcoming release
g77-2.95. (egcs-19990623)

The problem seems to be after the assembler run. If i compile t.f into t.s
and use g77 -o t t.s; ./t instead i get the same irregular runs.

ldd t gives:
libm.so.6 => /lib/libm.so.6 (0x40008000)
libc.so.6 => /lib/libc.so.6 (0x40022000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)       

(it's the same for segfaulting and running t's)

I tried it whithin gdb:
gdb t
run
Program received signal SIGSEGV, Segmentation fault.
0x804d043 in l_write ()
(gdb) where
#0  0x804d043 in l_write ()
#1  0x8048e3d in do_lio ()
#2  0x8048df6 in MAIN__ ()
#3  0x804b2d9 in main ()            

-- 
esa$ gcc -Wall -o ariane5 ariane5.c
ariane5.c: 666: warning: long float implicitly truncated to unsigned type
esa$ ariane5