What flags do you set for your GFORTRAN debugger/compiler to catch faulty code?

by

Bare minimum

-Og/-O0

-O0 basically tells the compiler to make no optimisations. Optimiser can remove some local variables, merge some code blocks, etc. and as an outcome it can make debugging unpredictable. The price for -O0 option is very slow code execution, but starting from version 4.8 GCC compilers (including the Fortran one) accept a newly introduced optimisation level -Og:

-Og

Optimize debugging experience. -Og enables optimizations that do not interfere with debugging. It should be the optimization level of choice for the standard edit-compile-debug cycle, offering a reasonable level of optimization while maintaining fast compilation and a good debugging experience.

So, if possible use -Og, otherwise use -O0.

-g

This option actually makes debugging possible by requesting the compiler to produce debugging information intended to be used by interactive debugger (GDB).

Addititonal

There are a plenty of them. The most useful in my opinion are:

-Wall to “enable all the warnings about constructions that some users consider questionable, and that are easy to avoid (or modify to prevent the warning), even in conjunction with macros.”

-Wextra to “enable some extra warning flags that are not enabled by -Wall.”

-pedantic to generate warnings about language features that are supported by gfortran but are not part of the official Fortran 95 standard. It possible to be even more “pedantic” and use -std=f95 flag for warnings to become errors.

-fimplicit-none to “specify that no implicit typing is allowed, unless overridden by explicit IMPLICIT statements. This is the equivalent of adding implicit none to the start of every procedure.”

-fcheck=all to “enable run-time tests”, such as, for instance, array bounds checks.

-fbacktrace to “specify that, when a runtime error is encountered or a deadly signal is emitted (segmentation fault, illegal instruction, bus error or floating-point exception), the Fortran runtime library should output a backtrace of the error.”

More Related Contents:

  1. How to pass allocatable arrays to subroutines in Fortran
  2. Where to put `implicit none` in Fortran
  3. gfortran does not allow character arrays with varying component lengths
  4. Fortran array cannot be returned in function: not a DUMMY variable
  5. How can I test a trigger function in GAS?
  6. Debugging iframes with Chrome developer tools
  7. How do I see the expanded macro code that’s causing my compile error?
  8. Attach IntelliJ IDEA debugger to a running Java process
  9. How to initialize two-dimensional arrays in Fortran
  10. How to use trace and dbg in Erlang to debug and trace my program?
  11. What is the difference between Step Into and Step Over in a debugger
  12. Step through JDK source code in IntelliJ IDEA
  13. How do I skip external code when debugging in VS Code
  14. Why are my random numbers always the same?
  15. What are the ways to pass a set of variable values through the subroutine to a function without common block?
  16. Debugging in Clojure? [closed]
  17. Is there a known issue relating to Windows 7 Kernel Symbols?
  18. How to debug Google Apps Script (aka where does Logger.log log to?)
  19. Android Studio IDE: Break on Exception
  20. Mac OS X R error “ld: warning: directory not found for option”
  21. How do I debug a stand-alone VBScript script?
  22. Visual Studio 2010 “Cannot find or open the PDB file”
  23. How to override a structure constructor in fortran
  24. Using do loop in a Fortran 90 program to read different number of lines for n frames?
  25. How to check release / debug builds using cfg in Rust?
  26. How to set level logging to DEBUG in Tomcat?
  27. Getting the state of variables after an error occurs in R
  28. Chrome Typescript debugging references wrong ‘this’
  29. Fortran SAVE statement
  30. how to access Angular2 component specific data in console?

Leave a Comment