Changes between Version 12 and Version 13 of Tools/Memory Checker

Timestamp:

Mar 31, 2010, 6:24:14 PM (14 years ago)

Author:

becoulet

Comment:

--

Tools/Memory Checker

@@ -118 +118 @@
 The Memory checker tool behavior can be configured through the use of the `SOCLIB_MEMCHK` environment variable. This variable may contains some flag letters:
 
- * The `T` flag can be used to raise a trap exception on suspicious memory access. This trap can be caught by the [wiki:Tools/GdbServer Gdb Server] tool.
- * The `R` flag can be added to report all allocator related operations reported by the Operating System.
- * The `C` flag can ba added to report all execution contexts creation and deletion operations.
- * The `S` flag can be added to report all context switch operations.
- * The `I` flag can be added to display all processor registers on each errors.
- * The `A` flag can be added to display offending memory access details.
+ * The '''T''' flag can be used to raise a trap exception on suspicious memory access. This trap can be caught by the [wiki:Tools/GdbServer Gdb Server] tool.
+ * The '''R''' flag can be added to report all allocator related operations reported by the Operating System.
+ * The '''C''' flag can ba added to report all execution contexts creation and deletion operations.
+ * The '''S''' flag can be added to report all context switch operations.
+ * The '''I''' flag can be added to display all processor registers on each errors.
+ * The '''A''' flag can be added to display offending memory access details.
+ * The '''L''' flag can be added to show all spin-lock takes and release.
 
 Here is an example invocation to obtain an interlaced Memory checker and `GdbServer` function calls trace, with trap exception and wait for gdb client connection on error: