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.

Sign up for GitHub

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

Jump to bottom

Modern Diag Manager crashes in debug mode because FMS_DIAG_ACCEPT_DATA is never set #1591

Open
uramirez8707 opened this issue Sep 18, 2024 · 0 comments · May be fixed by #1610
Open

Modern Diag Manager crashes in debug mode because FMS_DIAG_ACCEPT_DATA is never set #1591

uramirez8707 opened this issue Sep 18, 2024 · 0 comments · May be fixed by #1610

Comments

@uramirez8707
Copy link
Contributor

Describe the bug
When running with the modern diag manager, ESM is debug mode is crashing with

forrtl: severe (194): Run-Time Check Failure. The variable 'fms_diag_object_mod_mp_fms_diag_accept_data_$FMS_DIAG_ACCEPT_DATA' is being used in '/gpfs/f5/gfdl_f/scratch/Niki.Zadeh/fre/FMS2024.03_mom6_20231130/esm4.2_compile/src/FMS/diag_manager/fms_diag_object.F90(718,1)' without being defined
Image              PC                Routine            Line        Source                                              
fms_esm4.2_compil  000000000E5F3707  diag_manager_mod_        1792  diag_manager.F90                                    
fms_esm4.2_compil  000000000E5E1A5E  diag_manager_mod_        1578  diag_manager.F90

In this case the code leaves here, so fms_diag_accept_data is never set.

To Reproduce
Run in debug mode (without openmp)

Expected behavior
Debug mode should work

System Environment
This happens in any system.

Additional context
N/A
@uramirez8707 uramirez8707 linked a pull request Oct 30, 2024 that will close this issue
Open
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Set fms_diag_accept_data uramirez8707/FMS
1 participant
@uramirez8707