Windbg 和查看 AppDomain 内容

发布于 2024-12-15 21:27:47 字数 1078 浏览 2 评论 0原文

我知道我们可以在 winbbg 中使用 !dumpdomain 命令来查看给定托管进程（例如 w3wp）中存在的各种应用程序域。

我在 LinqPad 中编写了一个小程序（来自 Visual C# 2010 Recipes A 问题解决方法的食谱 3-1），以创建自定义 AppDomain。这就是我面临问题的地方。我无法使用 Windbg 查看此应用程序域。换句话说，这个应用程序域是在哪里创建的？它是否托管在 LinqPad 进程内？如果不是，那么哪个进程正在托管此自定义应用程序域？

我尝试将 LinqPad.exe 附加到 Windbg 并发出 !dumpdomain 命令，但出现以下错误：

找不到运行时 DLL (clr.dll)，0x80004005 扩展命令需要 clr.dll 才能有事可做。

代码：

void Main()
{
    AppDomainSetup setUpInfo = new AppDomainSetup();

    setUpInfo.ApplicationBase = @"C:\MyRootDirectory";
    setUpInfo.ConfigurationFile = "MyApp.config";
    setUpInfo.PrivateBinPath = "bin;plugins;external";

    AppDomain newDomain = AppDomain.CreateDomain("My New Domain",null,setUpInfo);

    Console.WriteLine("Main method complete.Press Enter");
    Console.ReadLine();
}

步骤如下：

运行程序。它等待用户按 Enter 键。
启动windbg。附加 LinqPad.exe。
发出命令：.load sos.dll 和 .load sosex.dll
发出命令 .reload
最后调用 !dumpdomain。此时 LinqPad 冻结。如果我关闭windbg，那么LinqPad也会关闭。

原文

I know we can use !dumpdomain command in winbbg to view the various app domains present in a given managed process(e.g. w3wp).

I wrote a small program(Recipe 3-1 from Visual C# 2010 Recipes A problem solution approach) in LinqPad, to create a custom AppDomain. This is where I am facing issues. I am not able to view this appdomain using windbg. In other words, where is this app domain created ? Is it hosted inside LinqPad process ? If not, then which process is hosting this custom appdomain ?

I tried attaching LinqPad.exe to windbg and issues !dumpdomain command but I got the following error :

Failed to find runtime DLL (clr.dll), 0x80004005 Extension commands
need clr.dll in order to have something to do.

Code :

void Main()
{
    AppDomainSetup setUpInfo = new AppDomainSetup();

    setUpInfo.ApplicationBase = @"C:\MyRootDirectory";
    setUpInfo.ConfigurationFile = "MyApp.config";
    setUpInfo.PrivateBinPath = "bin;plugins;external";

    AppDomain newDomain = AppDomain.CreateDomain("My New Domain",null,setUpInfo);

    Console.WriteLine("Main method complete.Press Enter");
    Console.ReadLine();
}

Steps Followed :

Run the program. It waits for the user to press Enter.
Start windbg. Attach LinqPad.exe.
issue commands : .load sos.dll and .load sosex.dll
Issue command .reload
Finally call !dumpdomain. At this point the LinqPad freezes. If I close the windbg, then LinqPad is also closed.

分享到QQ

分享到微博