Changes between Version 12 and Version 13 of Archer/DDT


Ignore:
Timestamp:
21/04/15 15:04:34 (6 years ago)
Author:
grenville
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Archer/DDT

    v12 v13  
    7272 
    7373It is probably best to ensure that the resources needed for the job you wish to debug match those requested in the interactive session - in this example I requested 4 interactive nodes and the job was configured to run on 4x12 MPI tasks each with 2 OMP threads for a total of 4 nodes. 
     74 
     75 
     76Memory Debugging 
     77 
     78There are several extra steps needed for memory debugging. The model must be linked with the appropriate library - this is easiest done by modifying the bld.cfg file. For the UM 8.2 example discussed here, I added 
     79 
     80{{{ 
     81-L $ALLINEA_TOOLS_DIR/lib/64 -Wl,--whole-archive -ldmallocthcxx -Wl,--no-whole-archive 
     82}}} 
     83 
     84at the beginning of the link line, the same should hold for other UM versions; then relink the code - at the ARCHER command line type 
     85 
     86{{{ 
     87module load allinea 
     88fcm build 
     89}}} 
     90 
     91make sure the new executable is copied to the appropriate place so that it is picked up when the model runs. 
     92 
     93Change the ddt line in qsatmos thus, ie remove -start and add -memory 
     94{{{ 
     95ddt  -noqueue -memory -n $UM_IOS_NPES -mpiargs "-N $NTASKS_PER_NODE -d $NTHREADS_PER_TASK -S $NTASKS_PER_NUMANODE -ss" $LOADMODULE >>$OUTPUT 
     96}}} 
     97 
     98Get an interactive session as before and follow the same submission procedure. You should now see