hooking a new intrinsic subroutine?

[Steve Kargl]

On Tue, Apr 20, 2004 at 04:49:45PM +0200, Lars Segerlund wrote:
> 
>  I'm looking into the failure of the random_seed(put=seed) call now,
>  however this used to work so I am a bit amazed since some of my old
>  test programs now fail, ( they used to work ), I probably have to
>  make a real testsuite.
> 
>  I don't have much time this week to look at it but it's in my
>  pipeline, it can't be very hard since it have worked before.
> 

I tried your suggestions of changing sz to sz+1 and sz=700.
Niether suggestion worked.  Doug Rabson has ported valgrind
to FreeBSD and it shows that memory is getting stomped.  I
also won't have time until the weekend to look into this 
any further.

troutmask:sgk[204] valgrind r
==88150== Memcheck, a memory error detector for x86-linux.
==88150== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
==88150== Using valgrind-2.1.0, a program supervision framework for x86-linux.
==88150== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
==88150== Estimated CPU clock rate is 1003 MHz
==88150== For more details, rerun with: -v
==88150== 
size =           624
==88150== Invalid read of size 4
==88150==    at 0x804D957: _gfortran_random_seed (in /home/sgk/tmp/r)
==88150==    by 0x80483C9: MAIN__ (r.f90:30)
==88150==    by 0x80486C7: main (in /home/sgk/tmp/r)
==88150==  Address 0xC is not stack'd, malloc'd or free'd
==88150== 
==88150== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==88150==    at 0x804D957: _gfortran_random_seed (in /home/sgk/tmp/r)
==88150==    by 0x80483C9: MAIN__ (r.f90:30)
==88150==    by 0x80486C7: main (in /home/sgk/tmp/r)
==88150== 
==88150== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

-- 
Steve