OSchip
/
llvm-project
mirror of https://github.com/THU-DSP-LAB/llvm-project.git
13
0
Fork 6
Code Issues Packages Projects Releases Wiki Activity

[lldb-mi] Fix misc. typos in comments. 

llvm-svn: 241448
This commit is contained in:
Bruce Mitchener 2015-07-06 14:37:53 +00:00
parent 76d650e8d7
commit 6b067074f9
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
lldb/tools/lldb-mi/MICmdMgr.h
View File

@ -27,7 +27,7 @@ class CMICmdBase;
//++ ============================================================================
// Details: MI command manager. Oversees command operations, controls command
// production and the running of commands.
// Command Invoker, Command Factory and Command Monitor while independant
// Command Invoker, Command Factory and Command Monitor while independent
// units are overseen/managed by *this manager.
// A singleton class.
// Gotchas: None.

6
lldb/tools/lldb-mi/MICmnLog.h
View File

@ -20,7 +20,7 @@
//++ ============================================================================
// Details: MI common code implementation class. Handle application trace
// activity logging. Medium objects derived from the Medium abstract
/// class are registered with this loggor. The function Write is called
/// class are registered with this logger. The function Write is called
// by a client callee to log information. That information is given to
// registered relevant mediums. The medium file is registered during
// *this logs initialization so it will always have a file log for the
@ -37,14 +37,14 @@ class CMICmnLog : public MI::ISingleton<CMICmnLog>
// Enumeration:
public:
//++
// Description: Data given to the Logger can be of serveral types. The Logger can be
// Description: Data given to the Logger can be of several types. The Logger can be
// set at levels of verbosity. Can determine how data is sent to one or
// mediums.
//--
enum ELogVerbosity
{ // Descriptions of what 'may' occur, depends ultimately on the medium itself. See the medium.
eLogVerbosity_FnTrace = 0x00000004, // Debug function stack call tracing
eLogVerbosity_DbgOp = 0x00000008, // Send a string to the debugguer for display (not implemented)
eLogVerbosity_DbgOp = 0x00000008, // Send a string to the debugger for display (not implemented)
eLogVerbosity_ClientMsg = 0x00000010, // A client using MI can insert messages into the log (not implemented)
eLogVerbosity_Log = 0x00000020 // Send to only the Log file.
};

2
lldb/tools/lldb-mi/MIDriver.h
View File

@ -46,7 +46,7 @@ class CMIDriver : public CMICmnBase,
// Enumerations:
public:
//++ ----------------------------------------------------------------------
// Details: The MI Driver has a running state which is used to help determin
// Details: The MI Driver has a running state which is used to help determine
// which specific action(s) it should take or not allow.
// The driver when operational and not shutting down alternates
// between eDriverState_RunningNotDebugging and

2
lldb/tools/lldb-mi/MIDriverMgr.h
View File

@ -32,7 +32,7 @@
// those objects (modules/components) to support it's own functionality).
// The Driver manager is the first object instantiated as part of the
// MI code base. It is also the first thing to interpret the command
// line arguments passed to the executeable. Bases on options it
// line arguments passed to the executable. Bases on options it
// understands the manage will set up the appropriate driver or give
// help information. Other options are passed on to the driver chosen
// to do work.