You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to debug a segfault for a new library in DFTB+ using Intel oneAPI. To get a meaningful traceback I would like to emit line markers with fypp but ifort likes non of the available options.
Using the cpp format the line markers are ignored due to bad format
ninja: Entering directory `_build'
[465/748] Building Fortran object prog/dftb+/CMakeFiles/dftbplus.dir/lib_common/status.f90.o
prog/dftb+/lib_common//home/awvwgk/projects/src/git/dftbplus/prog/dftb+/include/common.fypp(1): warning #5117: Bad # preprocessor line
# 9 "prog/dftb+/lib_common//home/awvwgk/projects/src/git/dftbplus/prog/dftb+/lib_common/status.F90" 2
-----------------------------------------------------------------------------------------------------^
[468/748] Building Fortran object prog/dftb+/CMakeFiles/dftbplus.dir/lib_common/globalenv.f90.o
prog/dftb+/lib_common//home/awvwgk/projects/src/git/dftbplus/prog/dftb+/include/common.fypp(1): warning #5117: Bad # preprocessor line
# 9 "prog/dftb+/lib_common//home/awvwgk/projects/src/git/dftbplus/prog/dftb+/lib_common/globalenv.F90" 2
--------------------------------------------------------------------------------------------------------^
[473/748] Building Fortran object prog/dftb+/CMakeFiles/dftbplus.dir/lib_common/assert.f90.o
prog/dftb+/lib_common//home/awvwgk/projects/src/git/dftbplus/prog/dftb+/include/common.fypp(1): warning #5117: Bad # preprocessor line
# 9 "prog/dftb+/lib_common//home/awvwgk/projects/src/git/dftbplus/prog/dftb+/lib_common/assert.F90" 2
-----------------------------------------------------------------------------------------------------^
While I get the an error with std formatted line markers
No, fypp never adds line breaks to line markers. What can happen, that a line marker appears before a continuation line (as it is the case above), which ifort can not handle. You can switch this with the --line-numbering-mode=nocontlines option. Unfortunately, it will not eliminate all the cases, as it will still result in line markers in two cases:
#:block / #:call statement has continuation lines in its argument:
#:block DEBUG
some_content&
&with_continuation line
#:endblock
Unfortunately, both cases seem to appear in DFTB+. The first one would have to big fixed in DFTB+, probably. The second one I would have to fix within fypp.
I'm trying to debug a segfault for a new library in DFTB+ using Intel oneAPI. To get a meaningful traceback I would like to emit line markers with
fypp
butifort
likes non of the available options.Using the
cpp
format the line markers are ignored due to bad formatWhile I get the an error with
std
formatted line markersNot sure what is going on here, but it seems to that fypp adding linebreaks in the line markers?
The text was updated successfully, but these errors were encountered: