http://blogs.msdn.com/tess/archive/2008/04/28/setting-breakpoints-in-net-code-using-bpmd.aspxFrom time to time I get questions like "our process spawns a lot of threads, how do we know who created them?" or "can I tell how many times we call this method?". You can answer both of these questions by setting breakpoints, and below is a simple samplesv-SECommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/tess/archive/2008/04/28/setting-breakpoints-in-net-code-using-bpmd.aspx#8436472Tue, 29 Apr 2008 06:03:10 GMT91d46819-8472-40ad-a661-2c78acb4018c:8436472greg roberts<p>Thanks, excellent resources for debugging!</p> http://blogs.msdn.com/tess/archive/2008/04/28/setting-breakpoints-in-net-code-using-bpmd.aspx#8443503Wed, 30 Apr 2008 17:27:29 GMT91d46819-8472-40ad-a661-2c78acb4018c:8443503Marc Sherman<p>Is there ever a case where code is not JITTED and therefore impossible to set a breakpoint?</p> http://blogs.msdn.com/tess/archive/2008/04/28/setting-breakpoints-in-net-code-using-bpmd.aspx#8443562Wed, 30 Apr 2008 17:49:13 GMT91d46819-8472-40ad-a661-2c78acb4018c:8443562Tess<p>It will be jitted when you first call the method, so when you need the breakpoint it will be there if you use !bpmd</p> http://blogs.msdn.com/tess/archive/2008/04/28/setting-breakpoints-in-net-code-using-bpmd.aspx#8444493Wed, 30 Apr 2008 21:59:47 GMT91d46819-8472-40ad-a661-2c78acb4018c:8444493Marc Sherman<p>So managed code is never interpreted, it's always JITTED and executed by the cpu?</p> http://blogs.msdn.com/tess/archive/2008/04/28/setting-breakpoints-in-net-code-using-bpmd.aspx#8447754Fri, 02 May 2008 01:19:05 GMT91d46819-8472-40ad-a661-2c78acb4018c:8447754Tess<p>yes</p>