Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 307169 - Last Review: April 7, 2003 - Revision: 4.0
BUG: Known Issues with Cordbg.exe
This article was previously published under Q307169
The following are known issues with the Common Language
Runtime (CLR) Debugging Services:
- Cordbg.exe sometimes stops responding (hangs) after it
attaches to a process.
In rare situations, where a process has
numerous threads, Cordbg.exe may stop responding after attaching to the
process. - Cordbg.exe does not work properly when you step through
statements in catch or finally blocks.
When you step through statements in a catch or
finally block, Cordbg.exe appears to stop responding. It may take several
attempts to step over a single statement. - Psapi.dll must be copied for debugging in Microsoft
Windows NT 4.0.
Psapi.dll, which is required for debugging, is not
included in Windows NT 4.0. This causes Mdm.exe to consume 100 percent of CPU
resources. Mdm.exe is a service that runs when the system boots. Furthermore,
when you try to open the Processes dialog box to see the list of processes on the computer, Mdm.exe,
DbgCLR, and/or Visual Studio .NET stop responding.
WORKAROUND: Copy Psapi.dll version number 4.0.1371.1 from the Microsoft
Visual Studio CD-ROM to the WINNT\System32 directory. - Cordbg.exe does not work well with JScript programs.
Cordbg.exe does not understand attributes of the unmanaged
JScript.dll. Before it reaches the program entry point or steps into a
function, it steps through JScript.dll in disassembly.
WORKAROUND: Use Visual Studio .NET instead. Cordbg.exe does not have all the
functionality that Visual Studio .NET has. - The user who has Debug programs permissions and is not in the Administrator group cannot debug
managed programs of other users.
In the current implementation of
runtime, only those users who have full Administrative permissions are allowed
to debug managed programs that are running under another account. For native
debugging, only Debug programs permissions are needed. - Function evaluation in Cordbg made on an object loaded in a
different application domain throws an exception.
If the class
instance is created in a different application domain than the domain in which
the program is running in, the function evaluation on that object throws an
exception. However, the calls made in the program on an object in a different
application domain still work properly. - At the end of a debugging session with Cordbg, when the
program being debugged is terminating, you may receive the following error
message from Cordbg:
hr=0x80131301, The debuggee has
terminated
- Function Evaluation is always implemented as a virtual
call.
Assume you have following classes in your program:
class Base
{
public virtual int Bar() { return 0; }
}
class Derived : Base
{
public override int Bar() {return 6; }
}
Derived x = new Derived();
Base y = x;
- Cordbg Help topic for newstr command is incorrect.
The Help topic for the cordbg newstr command incorrectly states that the parameter is "class."
Instead, the parameter should be "string." The string after the command should
be entered without any "".
Microsoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
APPLIES TO
- Microsoft .NET Framework Software Development Kit 1.0 Service Pack 2
- Microsoft .NET Framework Software Development Kit 1.0 Service Pack 2
- Microsoft .NET Framework Class Libraries 1.0
- Microsoft .NET Framework Class Libraries 1.1
| kbbug kbpending kbreadme KB307169 |
Retired KB Content DisclaimerThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate