BUG: Known Issues with the Common Language Runtime Debugging Services (309333)
The information in this article applies to:
- Microsoft .NET Framework 1.0
- Microsoft Windows .NET Framework 1.1
- Microsoft .NET Framework Class Libraries 1.0
- Microsoft Windows .NET Framework Class Libraries 1.1
This article was previously published under Q309333 SYMPTOMS The following are known issues with the Microsoft Common
Language Runtime (CLR) Debugging Services:
- ICorDebugEval::Abort cannot stop a function evaluation when the process is stopped.
ICorDebugEval::Abort works only when the process is running. If the process is
stopped, the abort request is not honored. - ICorDebugManagedCallback ::UnloadModule is not called for all the loaded modules when the program
terminates on Microsoft Windows 9x-based
computers.
On a Windows 9x-based computer,
the developers of the managed debugger/profiler tools should not expect that,
for each module that is loaded into the runtime and for which the ICorDebugManagedCallback::LoadModule is called, the corresponding ICorDebugManagedCallback ::UnloadModule callback will be called as well.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 5/28/2003 |
|---|
| Keywords: | kbMiscTools kbDebug kbbug kbpending kbreadme KB309333 |
|---|
|