FEAP windows Installation

[ad10]

Dear all,

I am able to install FEAP 8.6 on Visual studio community 2019 with one API, feap.exe generated too. But the issue here is, as soon as I launch the feap.exe it crashes immediately. Can you please tell me whats I am missing here?

Code: [Select]

1>Build log written to  "file://C:\Users\ajink\Feapp\feap\feap\Lib86\x64\Release\BuildLog.htm"
1>Lib86 - 0 error(s), 0 warning(s)
2>------ Build started: Project: feap (IFORT), Configuration: Release x64 ------
2>Compiling manifest to resources...
2>Microsoft (R) Windows (R) Resource Compiler Version 10.0.10011.16384
2>Copyright (C) Microsoft Corporation.  All rights reserved.
2>Linking...
2>LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; use /NODEFAULTLIB:library
2>Embedding manifest...
2>
2>Build log written to  "file://C:\Users\ajink\Feapp\feap\feap\feap\x64\Release\BuildLog.htm"
2>feap - 0 error(s), 1 warning(s)
========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

[ad10]

It opens and crashes when I gave any Input as 'Isolid.txt' in the filename.

[Prof. S. Govindjee]

For this last screenshot, you are entering Isolid.txt as the file name; I presume you then hit the RETURN key.  Is that when it crashes? or does it continue to asking you to confirm the file names and crash after you accept them?

[ad10]

yeah, it crashes as soon as I 'Enter'. Indirectly saying, FEAP close downs. Any reasons why it happening is it due to compiler?

[Prof. S. Govindjee]

I have not seen this error before.
You will need to perform some debugging to figure out what is going on.

The input prompt that you see is printed at program/filnam.f:137 and program/filnam.f:142.  The input is collected using windows/cinput.f into a string called record.  The only way that the code should exit at this point is if your filename was 'stop', 'exit', or 'quit'.

My suggestion is to put some debugging code into program/filnam.f to figure out what is going wrong.  If you have a debugger, then you can put a break point at line 137 in filnam.f and then step through the code to see what is causing the problem.

[Prof. S. Govindjee]

Did you have any luck tracking down this issue and fixing it?  I have just installed the latest Intel compilers on Windows and I now see this problem.  I have even created a 6 line stand alone program that has the same error.  The problem is the the read(*,'(a)') record line in windows/cinput.f and its interaction with some system level routines, but I have not been able to figure out if this is a FEAP error or a compiler error.

[ad10]

Prof., I tried but was not able to figure it out. So meanwhile, I decided to shift to ubuntu. But errors occur after updating the visual studio and new compiler.

[Prof. S. Govindjee]

I have verified that there is an error in Intel's latest compiler release.  It is recommended to avoid upgrading to the oneAPI version that provides IFORT version 2021.4.0.  The bug is pretty severe as it breaks the read( ) command.

Hopefully a new version is released soon.