[MITgcm-devel] help with debugging flags during compilation

[An Nguyen]

Hello mitgcm gurus,

For the last 2 years I've been having problem with the mitgcm crashing right out of the gate without producing any STDOUT or STDERR or any message at all on the various computing nodes we have at UT Austin, and the only help tech-support can provide us so far is a message saying that we need to do our own debugging.   

I'd like to ask for some help with the flags needed to remove all optimization options when compiling the mitgcm (with ifort) in order to enter debug mode such as dbg or this ddt tool they suggested (https://portal.tacc.utexas.edu/software/ddt <https://portal.tacc.utexas.edu/software/ddt>) .  The genmake2 various flags are very elaborate with various options for CFLAGS, FFLAGS, FOPTIM that are really beyond my comprehension (I spent 5 hours last night fiddling around and didn't succeed), so I'm hoping to get some suggestions on what I need to set: would stripping ALL CFLAGS and FFLAGS and FOPTIM and only use 

FFLAGS='-g'
FOPTIM='-O0'
CFLAGS=''

an option?  Any suggestion, including a sampled very-stripped-down optfile would be very helpful for me.  I can provide more information (within my comprehension) if needed.

Many thanks,
An

An T Nguyen, Ph.D. 
Institute of Computational Engineering and Sciences 
The University of Texas at Austin, 
201 East 24th Street, POB 4.234, 
Austin, TX 78712, USA 
Phone: (512) 471-4207 
<atnguyen at ices.utexas.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-devel/attachments/20180227/54a8ae29/attachment.html>