Changes between Version 7 and Version 8 of DebugProtocol

Timestamp:

06/06/11 18:07:48 (14 years ago)

Author:

Brandon Shroyer

Comment:

—

DebugProtocol

@@ -17 +17 @@
  * The reporter's {{{.bashrc}}} and {{{.bash_profile}}} contents.
 
-5.  The ticket owner should then try to isolate the source of the problem by:
-  * Running with debug flags turned on (and fixing any pointer/allocation issues).
-  * If no pointer/memory errors turn up then they should try the following options:
+5.  Run the problem with debug flags turned on.  If any pointer or memory allocation issues are found, then fix them first.
+
+6.  If no pointer/memory errors are found and the problem persists, then try the following options:
     * Lower the domain resolution.
     * Turn off AMR (i.e., set {{{MaxLevel}}} in {{{global.data}}} to 0).
@@ -29 +29 @@
   The goal here is to simplify the setup by turning off extra features until the error no longer manifests.  Once the error goes away, then try switching back on things that had been turned off until you have the closest thing to the original setup that still works.  The remaining deactivated features should provide further clues about the fault.
 
-6.  Prepare a report (i.e., summary comment on the ticket) for weekly debug meetings.  This comment should describe the results of the ticket owner's tests.  If possible, the ticket owner should also recommend further courses of action.
+7.  Prepare a report (i.e., summary comment on the ticket) for weekly debug meetings.  This comment should describe the results of the ticket owner's tests.  If possible, the ticket owner should also recommend further courses of action.