hodgesse1 / rfortran

Automatically exported from code.google.com/p/rfortran
0 stars 0 forks source link

runtime error when calling Rinit and checking for NULL pointers #49

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
*** What steps will reproduce the problem?

1. Open any project using RFortran routine Rinit.

2. Use Project settings > Fortran > Runtime: Check for NULL pointers and
allocatable array references: Yes (slackingly, the default is "no")

3. Run project.

*** What is the expected output? What do you see instead?

When executing Rinit, get runtime error (crushing the code):

"Debug Assertion Failed: Attempt to use NULL pointer bluh-blug."

*** What Fortran compiler (name and version number) are you using?

IVF 11

*** Please provide any additional information below.

The problemizer is the first argument of createprocess, which is (legally),
a NULL pointer. The runtime error appears bogus, but still... crushes the
code..

This issue complicates debugging of programs reliant on RFortran.

While this can be avoided by disabling checks for NULL pointer references,
the check for NULL pointers is quite useful for general debugging.

More generally, and philosophically, using Rfortran should not force you to
lower the stringency of debug and/or runtime checks.

Original issue reported on code.google.com by dmitri.k...@gmail.com on 15 Sep 2009 at 12:21

GoogleCodeExporter commented 8 years ago
This issue does not appear to be a problem in v2.0.0

Original comment by mark.th...@gmail.com on 19 Feb 2010 at 5:46