Changes between Version 5 and Version 6 of Documentation/UserGuide/SegmentationFault


Ignore:
Timestamp:
2020-04-20T10:01:26+02:00 (4 years ago)
Author:
dgoll
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Documentation/UserGuide/SegmentationFault

    v5 v6  
    11= How to find a segmentation error or a floating invalid error = 
    22Author: D. Solyga[[BR]] 
    3 Last revision: J. Ghattas 2020/02/28 
     3Last revision: D. Goll 2020/04/20 
    44 
    55 
    66== Segmentation errors == 
    77 
    8 Segmentation errors indicate issues with the memory which are often caused by ill-defined array dimensions. The dimension of your arrays can be checked by changing the settings of the compiler. Note that running the code will take a lot longer! Run the code on a single point test-case to avoid wasting computing resources. Segmentation faults can be trapped directly by the compiler. Check carefully the error messages written by the compiler.  
     8'''What is it?:''' Segmentation errors indicate issues with the memory which are often caused by ill-defined array dimensions.  
    99 
    10 See here how to compile in debug mode: wiki:Documentation/UserGuide/CompileMethods 
     10'''How to address it:''' The dimension of your arrays can be checked by changing the settings of the compiler. Segmentation faults can be trapped directly by the compiler. Check carefully the error messages written by the compiler.  
     11 
     12 
     13 
     14See here how to '''compile in debug mode'''. Note that running the code will take a lot longer! Run the code on a single point test-case '''(ADD LINK TO HOW TO RUN SINGLE PIXEL)''' to avoid wasting computing resources.: wiki:Documentation/UserGuide/CompileMethods 
     15 
     16 
    1117 
    1218== Floating invalid == 
    13 If during run time, you got an error saying '''floating invalid...''', compiling with debug options might give more information while running the model again. Hopefully, when you run the model again, you'll get the line number where the model crashed.  
     19'''What is it?:''' During an arithmetic operation, the floating-point values used in a calculation were invalid for the type of operation requested or invalid exceptional values. For example, the error can occur if you request a log of the floating-point values 0.0 or a negative number. 
    1420 
    15 Note that the line number given by the compiler corresponds to the preprocessed file. For ORCHIDEE, these files are found in modipsl/modeles/ORCHIDEE/build/ppsrc/. Check these files to know which is the corresponding line.  
     21'''How to address it:''' If during run time, you got an error saying floating invalid..., compiling with debug options might give more information while running the model again. Hopefully, when you run the model again, you'll get the line number where the model crashed.  
    1622 
    17 See here how to compile in debug mode: wiki:Documentation/UserGuide/CompileMethods 
     23Note that the '''line number''' given by the compiler corresponds to the preprocessed file. For ORCHIDEE, these files are found in modipsl/modeles/ORCHIDEE/build/ppsrc/. Check these files to know which is the corresponding line.  
    1824 
     25See here how to '''compile in debug mode'''. Note that running the code will take a lot longer! Run the code on a single point test-case '''(ADD LINK TO HOW TO RUN SINGLE PIXEL)''' to avoid wasting computing resources: wiki:Documentation/UserGuide/CompileMethods 
     26