Digging deeper into managed code with Visual Studio: Using SOS

re: Digging deeper into managed code with Visual Studio: Using SOS

barrkel — Wed, 06 Sep 2006 11:14:46 GMT

Great info! Thanks.

BTW, when using windbg + sos to debug, what breakpoint (native: bp / bu) is best to set in order to use managed breakpoints (thus both !name2ee and !bpmd probably needed)? With a breakpoint on loading of mscorwks or calling of various CLR functions, when is the CLR booted up enough so that !name2ee etc. can work?

re: Digging deeper into managed code with Visual Studio: Using SOS

vancem — Wed, 06 Sep 2006 19:46:23 GMT

The subject of using SOS in windbg will be the subject of a future blog, however, I can quickly answer your question.
The !bpmd (Breakpoint MethodDescriptor), is a command that will set a breakpoint on a managed method by name. For example in the example the command

!bpmd InspectingManagedCode.exe Program.Main

Will set a breakpoint in the ‘Main’ routine of the example program in the ZIP file. Note that UNLIKE the !name2ee SOS command (which looks up a method, or class by name), the method being referenced in the !BPMD command does NOT need to be loaded to work (it sets a ‘deferred’ breakpoint).

However to use ANY SOS command, you need to load SOS, and it turns out that SOS needs the .NET runtime dlls ‘mscorwks.dll’ to be loaded before it can load. There are a variety of techniques you can use. The one I use is

bu mscorwks!EEStartup

This sets a breakpoint at the ‘EEStartup’ method in the .NET runtime DLL ‘mscorwks. When this breakpoint hits you can do the command

.loadby sos mscorwks

Which tells windbg to load the sos.dll by searching the in the directory where mscorwks lives. Once loaded you can execute a ! bpmd command.

Finally if you need !name2ee to work and the module is not yet loaded, you should set a breakpoint (using !bpmd command), in the module of interest, run to that breakpoint (now it is loaded), and then do the !name2ee command.

Useful Links

Andy's Biztalk & BAM Blog — Wed, 23 May 2007 21:59:58 GMT

.NET Programming and Practices Programming with .NET Best Practices for Handling Exceptions Patterns

.Net B/S结构程序资源索引

PrideRoCK — Wed, 25 Jul 2007 11:16:13 GMT

.net b/s 结构程序性能优化索引如何最大限度提高.NET的性能如何最大限度提高.NET的性能(续) 客户端调用服务器端方法——ASP.NET AJAX(Atlas)、Anthem.NET和Ajax.NET Professional实现之小小比较 net b/s 数据库Microsoft SqlServer 2005 优化索引 SQL Server性能调优入门(图文版) 怎么捅破那层纸? 怎么捅破那层纸?(续) Sql Server Performance Tuning(捅破窗户纸续2)..

Paradigms around Debugging Memory leaks

Mike Stall's .NET Debugging Blog — Fri, 14 Sep 2007 09:28:53 GMT

In native code, memory is explicitly managed by the program calling Malloc()/Free() (or comparable APIs).

MSDN Blog Postings » Paradigms around Debugging Memory leaks

MSDN Blog Postings » Paradigms around Debugging Memory leaks — Fri, 14 Sep 2007 11:04:57 GMT

PingBack from http://msdnrss.thecoderblogs.com/2007/09/14/paradigms-around-debugging-memory-leaks/

re: Digging deeper into managed code with Visual Studio: Using SOS

ananda84 — Tue, 12 Feb 2008 13:06:53 GMT

Good information.

Is it possible to set breakpoint on native api functions like kernel32!CreateFileW using VS 2005+SOS?

Casting using [isinst] and [castclass]

Code Details — Sat, 24 May 2008 00:48:20 GMT

Much has been written about casting in .NET and how the various options we have at our disposal affect

Advanced Debugging Resources : ????????????????????? TAHETA.ORG

Advanced Debugging Resources : ????????????????????? TAHETA.ORG — Tue, 20 Jan 2009 05:59:02 GMT

PingBack from http://www.taheta.org/?p=192