Hi Michel,
as we found out, creating and switching build configurations
should work with the next (minor?) update of Photran.
Once that works, you could simply save your settings to your debug
config, or create a second with even stronger debug flags (at
least for the Intel Fortran Compiler
there are many more debug options). Since everybody probably has
different debug preferences, that should be the way to go, instead
of having
all kinds of flags enabled by default ... do you agree?
Best
Daniel
PS: Thanks for the hint about renaming unused f90 files to txt to
have them excluded from indexing. Haven't tried it yet, but I am
sure it will do the trick once I enable
refactoring again.
On 03/16/2011 11:24 AM, DEVEL Michel wrote:
Dear Photran developpers,
I suggest adding -fcheck=all to the default GCC Debug config (or
at least -fcheck=bounds),
and the equivalent for the Intel compiler.
Apparently it is not in the default (-g) since adding it in
Preferences/Fortran Build/ Tool settings/GNU Fortran
Compiler/Debugging/Other debugging flags helped me get out of a
bad SIGSEGV in my code.
--
sincerely_yours.txt
Sincerely yours,
Michel DEVEL
_______________________________________________
photran mailing list
photran@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/photran
|
