BUG: Known Issues with the Common Language Runtime Debugging Services

Article translations Article translations
Article ID: 309333 - View products that this article applies to.
This article was previously published under Q309333
Expand all | Collapse all

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.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Properties

Article ID: 309333 - Last Review: February 21, 2007 - Revision: 4.5
APPLIES TO
  • Microsoft .NET Framework 1.0
  • Microsoft .NET Framework 1.1
  • Microsoft .NET Framework Class Libraries 1.0
  • Microsoft .NET Framework Class Libraries 1.1
Keywords: 
kbbug kbmisctools kbreadme kbdebug kbpending KB309333

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com