blocks|key|1537215|text|当我从NT4.0服务器上收到.dmp文件时，我就会用到它--+MSVC不会加载这些旧格式的文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1537216|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have used it when I've been sent .dmp files from an NT4.0 server - MSVC won't load these old format files.

blocks|key|1752232|text|轻量级，无需在客户端机器上安装即可运行，速度快，可调试内核模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1752233|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Lightweight, can be run without installing it on a client's machine, fast, can debug kernel mode.

blocks|key|1537336|text|如果你想知道为什么你应该使用windbg而不是Visual+Studio，那么你需要阅读Advanced+Windows+Debugging。任何时候你需要调试一个真正丑陋的问题，windbg都有比Visual+Studio更好的技术。Windbg具有更强大的脚本语言，并允许您编写DLL来自动处理困难的问题。它将安装gflags.exe，这使您可以更好地控制堆以调试内存覆盖。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1537337|你实际上不需要运行安装，你只需要复制文件就可以了。此外，它还安装了adsplus.vb，因此您可以对正在运行的进程进行微型转储。它也很容易设置来执行远程调试。没有什么比能够在自己的办公桌上调试问题，而不是对抗测试PC上闪烁的15英寸显示器更好的了。|1537338|对于日常代码编写，我使用Visual+Studio，但一旦您需要从其他计算机开始调试问题或发现自己处于非常丑陋的情况下，windbg是唯一的选择。花一些时间学习windbg是一项很好的投资。另外，如果你看一下崩溃转储，你会发现有两个很棒的资源，http://www.dumpanalysis.org/blog和http://blogs.msdn.com/ntdebugging/default.aspx，它们使用windbg进行所有的调试。|1537339|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321374460|1|http://www.dumpanalysis.org/blog|2|http://blogs.msdn.com/ntdebugging/default.aspx^0|18|Q|0|0|0|3E|W|1|4B|1A|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

If you are wondering why you should use windbg over Visual Studio, then you need to read <a href="https://rads.stackoverflow.com/amzn/click/com/0321374460" rel="noreferrer" rel="nofollow noreferrer">Advanced Windows Debugging</a>. Any time you need to debug a truly ugly problem windbg has better technology to do it with than Visual Studio. Windbg has a more powerful scripting language and allows you to write DLLs to automate difficult problems. It will install gflags.exe, which gives you better control over the heap for debugging memory overwrites. 

You don't actually need to run the install, you can just copy the files over and be ready to go. Also it installs adsplus.vb, so you can take mini-dumps of running processes. It is also very easy to setup to perform remote debugging. There is nothing better than being able to debug a problem from your own desk instead of fighting the 15" monitor that flickers on a test PC. 

For day to day code writing I use Visual Studio, but once you need to start debugging problems from other computers or find yourself in a very ugly situation, windbg is the only way to go. Spending some time learning windbg is a great investment. Also if you look at crash dumps there are two great resources, <a href="http://www.dumpanalysis.org/blog" rel="noreferrer">http://www.dumpanalysis.org/blog</a> and <a href="http://blogs.msdn.com/ntdebugging/default.aspx" rel="noreferrer">http://blogs.msdn.com/ntdebugging/default.aspx</a> that do all their debugging using windbg.

blocks|key|1752350|text|您不需要指定是调试本机代码还是托管代码。这不会影响答案，WinDbg对两者都非常有用，但许多人认为在调试.NET应用程序时，WinDbg在某种程度上不那么重要。事实并非如此。额外的好处是，您可以通过使用.NET扩展在WinDbg中调试您的.NET应用程序来了解更多关于WinDbg平台的工作原理。在WinDbg中运行(或附加到)您的.NET应用程序，然后键入...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1752351|.loadby+sos+mscorwks|code-block|syntax|javascript|1752352|...to请确保为所使用的CLR版本加载了正确的扩展。然后键入...|1752353|!help|1752354|..。查看SOS扩展中有哪些命令可用。|1752355|我听人开玩笑说微软只有一个开发工具，那就是WinDbg。你可能想要调试的所有东西都在那里，或者在一个扩展中。当然，这些东西的子集在VS中也是可用的，具有更友好的UI...:-)|1752356|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

You don't specify whether you're debugging native or managed code. It doesn't affect the answer, WinDbg is extremely useful for both, but many people believe that WinDbg is somehow less relevant when debugging .NET apps. Not so. As a bonus, you can learn a lot about how the .NET platform works by debugging your .NET app in WinDbg with the SOS extension. Run up (or attach to) your .NET app in WinDbg and type...

<pre><code>.loadby sos mscorwks
</code></pre>

...to be sure that you load the right extension for the version of the CLR in use. Then type...

<pre><code>!help
</code></pre>

... to see what commands are available in the SOS extension.

I've heard it joked that Microsoft only has one developer tool, and it's WinDbg. Everything you could possibly want for debugging is in there, or in an extension. Sure, a subset of those things are also available in VS with a friendlier UI... :-)

blocks|key|1752405|text|最新的visual+studio是否仍然缺少windbg的"-o“的等价物，使调试器自动附加到子进程？对于必须从复杂的.bat文件运行的应用程序，或者派生并退出父进程的应用程序非常有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1752406|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Is the latest visual studio still missing an equivalent to windbg's "-o" that makes the debugger automatically attach to child processes? Very useful for apps that must be run from a complicated .bat file, or apps that fork and exit the parent process.

blocks|key|1752456|text|我一直很喜欢监视和跟踪功能：'wt‘->它在发生函数调用时将所有函数调用打印到输出窗口。这是相当酷的东西！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1752457|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I always liked the watch and trace feature: 'wt'
-> It prints to the output window all the function calls as they happen. That was pretty cool stuff!

What are the major reasons for using <a href="http://en.wikipedia.org/wiki/WinDbg" rel="noreferrer">WinDbg</a> vs the Visual Studio debugger?

And is it commonly used as a complete replacement for the Visual Studio debugger, or more for when the need arises.

Why use WinDbg vs the Visual Studio (VS) debugger?

Visual Studio

远程调试

服务器

调试器

使用而不是Visual Studio调试器的主要原因是什么？它是否通常用作Visual Studio调试器的完全替代品，或者在需要时使用更多。

问为什么使用WinDbg而不是Visual Studio ( vs )调试器？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么使用WinDbg而不是Visual Studio ( vs )调试器？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么使用WinDbg而不是Visual Studio ( vs )调试器？
EN