jgarcia-2 wrote:
>
> Yes That's it! Thanks a lot!!
> Changing UNIT=5 in the F95 code by UNIT=7 solves the collision.
>
> Thank you very much Charlie, I've spent a lot of hours with this.
>
I'm glad it worked!
Google seems to indicate that units 0, 5, 6, 100, 101 and 102 are speci
Yes That's it! Thanks a lot!!
Changing UNIT=5 in the F95 code by UNIT=7 solves the collision.
Thank you very much Charlie, I've spent a lot of hours with this.
Still
R -d valgrind --vanilla < foofortran.Rcheck/foofortran-Ex.R
gives 3 errors (two "Invalid read of size 8" and one "Sys
jgarcia-2 wrote:
>
> Hi,
> I've stripped all the code, and it seems that any simple attempt to
> open/close a file from fortran is the cause of the error, and the error
> appears in f77 as well as in f95 code. Please, find attached a foo package
> that reproduce the errors, it should build/check
Hi,
I've stripped all the code, and it seems that any simple attempt to
open/close a file from fortran is the cause of the error, and the error
appears in f77 as well as in f95 code. Please, find attached a foo package
that reproduce the errors, it should build/check/install without any
problem (it
Please try running this under valgrind (see 'Writing R Extensions').
The most likely cause is that the Fortran code is corrupting its or
R's memory. You may need a build of R set up to instrument R
allocations (see the manual for details).
On Tue, 13 Apr 2010, jgar...@ija.csic.es wrote:
Hi
Hi all,
I'm preparing a package which uses .Fortran to interface a Fortran 95
function. This F95 function simply receives the name of a file from R,
opens this file and forwards its content to a F95 module, which, in turn,
makes the real computation. The F95 module is a pre-existing one and I'm
tr
