Changes between Version 2 and Version 3 of Tools/Memory Checker

Timestamp:

Jan 29, 2009, 9:48:28 PM (15 years ago)

Author:

Joel Porquet

Comment:

typos

Tools/Memory Checker

@@ -34 +34 @@
 === Suspicious memory access reporting ===
 
-Suspicious memory accesses produce a message on simulator `stdout` stream. This simulation is not stopped anyway.
+Suspicious memory accesses produce a message on simulator `stdout` stream. This simulation is not stopped though.
 
-An exception can be reported to an optional GdbServer module to stop processors execution when a suspicious memory access happend. This enables further analisys of buggy software. When using the Memory checker with the GdbServer, the Memory checker must wrap the processor directly and must be wrapped in the GdbServer.
+An exception can be reported to an optional GdbServer module to stop processors execution when a suspicious memory access happened. This enables further analysis of buggy software. When using the Memory checker with the GdbServer, the Memory checker must wrap the processor directly and must be wrapped in the GdbServer.
 
 == Usage ==
@@ -67 +67 @@
 === Using an instrumented operating system ===
 
-The running operating system must communicate with the Memory checker to report information about context creation, stack range and allocator operations. This is done through read/write access to specifc memory locations which are intercepted by the Memory checker and not forwarded to the rest of the platform.
+The running operating system must communicate with the Memory checker to report information about context creation, stack range and allocator operations. This is done through read/write accesses to specific memory locations which are intercepted by the Memory checker and not forwarded to the rest of the platform.
 
 Currently the only known supported operating system is [http://www.mutek.fr MutekH] with Mips processor. Other processors are partially supported, only memory allocation checks are performed. To use the memory checker with MutekH, simply add the `CONFIG_SOCLIB_MEMCHECK` configuration token to your configuration file.
 
 Note:
- * An instrumented operating system can not be used without the ISS Memory checker module as memory access won't be intercepted and may cause bus error or side effects.
+ * An instrumented operating system can not be used without the ISS Memory checker module as memory accesses won't be intercepted and may cause bus error or side effects.
  * The default base address for the register bank of the memory checker is 0x00004200. This address can be changed but must stay close to 0 to fit on some processor instruction immediate field. You should consider this if you already have components at these addresses.
- * The Memory checker registers bank is protected by a magic value and has almost no chance being modified by an other running software.
+ * The Memory checker registers bank is protected by a magic value and is unlikely to be modified by an other running software.