Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seg fault with GFortran 9 #347

Closed
pjstanle opened this issue Oct 12, 2019 · 5 comments
Closed

Seg fault with GFortran 9 #347

pjstanle opened this issue Oct 12, 2019 · 5 comments

Comments

@pjstanle
Copy link

Hello!

I'm trying to get OpenFAST running. I have cloned, installed, and tested with the following code from the documentation:

image

However, I get the following failures when performing the regression tests:

image
image

When I run a verbose test, I find that the issue (I think) is a segmentation fault regarding a .log file.

image

I have checked, and the .log file exists at the indicated path, but it is blank (not sure if this is a problem). I tried updated my gcc compiler, and have experienced the same issue. Are there any thoughts on how to solve this problem?

Thanks in advance for any solutions

@rafmudaf rafmudaf self-assigned this Oct 14, 2019
@rafmudaf
Copy link
Collaborator

What is your system information?

System Information (please complete the following information):

  • OS: [e.g. Ubuntu 14.04 or macOS 10.12]
  • Compiler: [e.g. GFortran 4.4]
  • Compiler settings: [e.g. CMake flags or other settings]

@pjstanle
Copy link
Author

OS: macOS 10.11.6
Compiler: GNU Fortran (Homebrew GCC 9.2.0_1) 9.2.0
Compiler settings: -DBUILD_TESTING=ON

@rafmudaf rafmudaf changed the title Regression Test Failure Seg fault with GFortran 9 Oct 17, 2019
@rafmudaf
Copy link
Collaborator

@pjstanle this is indeed a bug! However, its only a problem with the highest level of compiler optimization (-O3) on the GNU Fortran compiler versions 8+. I've made a fix and pushed it to my fork: the fix. After more testing, I'll issue a pull request to bring this to the dev branch.

In the meantime, you could take my changes and incorporate them into your repository or compiler with a lower optimization level. To do that, use CMake:

cmake .. -DCMAKE_BUILD_TYPE=RELWITHDEBINFO
make install

@rafmudaf
Copy link
Collaborator

This CMake build type uses -O2 optimization rather than -O3.

@rafmudaf
Copy link
Collaborator

@pjstanle the fix for this has been merged into the dev branch. Comment again here if you still run into problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants