Changes between Version 8 and Version 9 of DebugProtocol

Timestamp:

06/06/11 18:35:12 (14 years ago)

Author:

Jonathan

Comment:

—

DebugProtocol

@@ -17 +17 @@
  * The reporter's {{{.bashrc}}} and {{{.bash_profile}}} contents.
 
-5.  Run the problem with debug flags turned on.  If any pointer or memory allocation issues are found, then fix them first.
+5.  Run the problem with debug flags turned on.  If any pointer or memory allocation issues are found, then fix them first.  If segfaults are other memory errors still occur without being caught by the compiler's error checking then 
+  * Make absolutely sure the stack size is large enough (preferrably unlimited)
+  * Run the problem somewhere where you can monitor the memory usage (on bluehive or on bluegene with totalview) and check that is within the available resources
+  * Run a much lower resolution run for a fraction of the runtime but with all of the physics turned on using valgrind or totalview and fix any errors that appear.
 
-6.  If no pointer/memory errors are found and the problem persists, then try the following options:
+6.  If no pointer/memory errors are found and the problem does not segfault but the problem persists, then try the following options:
     * Lower the domain resolution.
     * Turn off AMR (i.e., set {{{MaxLevel}}} in {{{global.data}}} to 0).