Changes between Version 10 and Version 11 of DebugProtocol
- Timestamp:
- 12/07/11 12:36:20 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DebugProtocol
v10 v11 20 20 * Make absolutely sure the stack size is large enough (preferrably unlimited) 21 21 * 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 22 * Run a much lower resolution run for a fraction of the runtime but with all of the physics turned on using valgrindor totalview and fix any errors that appear.22 * Run a much lower resolution run for a fraction of the runtime but with all of the physics turned on using [DeBugging valgrind] or totalview and fix any errors that appear. 23 23 24 24 6. If no pointer/memory errors are found and the problem does not segfault but the problem persists, then try the following options:
