[Lldb-commits] [lldb] r124586 - /lldb/trunk/source/Plugins/Process/Utility/EmulateInstruction.h

Johnny Chen johnny.chen at apple.com
Mon Jan 31 09:37:39 PST 2011


Author: johnny
Date: Mon Jan 31 11:37:39 2011
New Revision: 124586

URL: http://llvm.org/viewvc/llvm-project?rev=124586&view=rev
Log:
Minor comment fix.

Modified:
    lldb/trunk/source/Plugins/Process/Utility/EmulateInstruction.h

Modified: lldb/trunk/source/Plugins/Process/Utility/EmulateInstruction.h
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/source/Plugins/Process/Utility/EmulateInstruction.h?rev=124586&r1=124585&r2=124586&view=diff
==============================================================================
--- lldb/trunk/source/Plugins/Process/Utility/EmulateInstruction.h (original)
+++ lldb/trunk/source/Plugins/Process/Utility/EmulateInstruction.h Mon Jan 31 11:37:39 2011
@@ -29,7 +29,7 @@
 /// - Predicting single step breakpoint locations
 /// - Emulating instructions for breakpoint traps
 ///
-/// Objects can be asked to read and instruction which will cause a call
+/// Objects can be asked to read an instruction which will cause a call
 /// to the read register callback to get the PC, followed by a read 
 /// memory call to read the opcode. If ReadInstruction () returns true, 
 /// then a call to EmulateInstruction::EvaluateInstruction () can be 
@@ -38,10 +38,10 @@
 ///
 /// Clients that provide the callbacks can either do the read/write 
 /// registers/memory to actually emulate the instruction on a real or
-/// virtual CPU, or watch to the EmulateInstruction::Context which
+/// virtual CPU, or watch for the EmulateInstruction::Context which
 /// is context for the read/write register/memory which explains why
 /// the callback is being called. Examples of a context are:
-/// "pushing register 3 onto to stack at offset -12", or "adjusting
+/// "pushing register 3 onto the stack at offset -12", or "adjusting
 /// stack pointer by -16". This extra context allows the generation of
 /// CFI information from assembly code without having to actually do
 /// the read/write register/memory.
@@ -56,7 +56,7 @@
 /// class that will soon be available.
 /// 
 /// Implmenting all of the instructions that affect the PC can then
-/// can then allow single step prediction support.
+/// allow single step prediction support.
 ///
 /// Implmenting all of the instructions allows for emulation of opcodes
 /// for breakpoint traps and will pave the way for "thread centric"





More information about the lldb-commits mailing list