summaryrefslogtreecommitdiff
path: root/src/debug
diff options
context:
space:
mode:
authorDan Moseley <danmose@microsoft.com>2019-05-01 22:49:50 -0700
committerJan Kotas <jkotas@microsoft.com>2019-05-01 22:49:49 -0700
commit78e2dd7a4dbe9846806215741783a0900f698159 (patch)
treef067b90ca2fb754e52183cae7572601a940b3c24 /src/debug
parent1744b9ab1d7e8a8654c621b3ab79eafb7afa0402 (diff)
downloadcoreclr-78e2dd7a4dbe9846806215741783a0900f698159.tar.gz
coreclr-78e2dd7a4dbe9846806215741783a0900f698159.tar.bz2
coreclr-78e2dd7a4dbe9846806215741783a0900f698159.zip
Adjust some terms (#24351)
Diffstat (limited to 'src/debug')
-rw-r--r--src/debug/di/process.cpp6
-rw-r--r--src/debug/ee/debugger.cpp4
2 files changed, 5 insertions, 5 deletions
diff --git a/src/debug/di/process.cpp b/src/debug/di/process.cpp
index 36b4b3a632..ae1dd03314 100644
--- a/src/debug/di/process.cpp
+++ b/src/debug/di/process.cpp
@@ -12225,7 +12225,7 @@ Reaction CordbProcess::TriageExcep1stChanceAndInit(CordbUnmanagedThread * pUnman
LOG((LF_CORDB, LL_INFO1000, "CP::TE1stCAI: Enter\n"));
#ifdef _DEBUG
- // Some Interop bugs involve threads that land at a crazy IP. Since we're interop-debugging, we can't
+ // Some Interop bugs involve threads that land at a bad IP. Since we're interop-debugging, we can't
// attach a debugger to the LS. So we have some debug mode where we enable the SS flag and thus
// produce a trace of where a thread is going.
if (pUnmanagedThread->IsDEBUGTrace() && (dwExCode == STATUS_SINGLE_STEP))
@@ -12784,7 +12784,7 @@ void CordbProcess::HandleDebugEventForInteropDebugging(const DEBUG_EVENT * pEven
STRESS_LOG1(LF_CORDB, LL_INFO1000, "W32ET::W32EL: Thread 0x%x is suspended\n", pEvent->dwThreadId);
}
- // For debugging crazy races in retail, we'll keep a rolling queue of win32 debug events.
+ // For debugging races in retail, we'll keep a rolling queue of win32 debug events.
this->DebugRecordWin32Event(pEvent, pUnmanagedThread);
@@ -13390,7 +13390,7 @@ DWORD GetDbgContinueFlag()
}
-// Some Interop bugs involve threads that land at a crazy IP. Since we're interop-debugging, we can't
+// Some Interop bugs involve threads that land at a bad IP. Since we're interop-debugging, we can't
// attach a debugger to the LS. So we have some debug mode where we enable the SS flag and thus
// produce a trace of where a thread is going.
#ifdef _DEBUG
diff --git a/src/debug/ee/debugger.cpp b/src/debug/ee/debugger.cpp
index e8e8de94c3..235a937cd6 100644
--- a/src/debug/ee/debugger.cpp
+++ b/src/debug/ee/debugger.cpp
@@ -261,7 +261,7 @@ bool IsGuardPageGone()
// We're not going to be called for a unmanaged exception.
// Should always have a managed thread, but just in case something really
- // crazy happens, it's not worth an AV. (since this is just being used as a hint)
+ // strange happens, it's not worth an AV. (since this is just being used as a hint)
if (pThread == NULL)
{
return false;
@@ -13171,7 +13171,7 @@ HRESULT Debugger::UpdateNotYetLoadedFunction(mdMethodDef token, Module * pModule
HRESULT hr = pModule->GetMDImport()->GetParentToken(token, &classToken);
if (FAILED(hr))
{
- // We never expect this to actually fail, but just in case it does for some other crazy reason,
+ // We never expect this to actually fail, but just in case it does for some other strange reason,
// we'll return before we AV.
CONSISTENCY_CHECK_MSGF(false, ("Class lookup failed:mdToken:0x%08x, pModule=%p. hr=0x%08x\n", token, pModule, hr));
return hr;