<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
<channel>
<title> .NET news &gt;&gt; Debug</title>
<link>http://www.dotnetcat.com/Debug/</link>
<description>.NET developer news by tags: C#, ASP.NET, VB.NET, database, security, performance and more</description>
<language>en-us</language>
<item>
<title>TraceTool 10.1: The Swiss-Army Knife of Trace</title>
<link>http://www.dotnetcat.com/news/Debug/id/8932/</link>
<pubDate>Fri, 16 May 2008 10:38:00 -0500</pubDate>
<description> <![CDATA[ A C#, C++, Delphi, ActiveX and Java trace framework and a trace viewer: Tail, outputDebugString, event log, and with Log4J, Log4Net, and Microsoft Enterprise Instrumentation Framework (EIF) support. This also comes with full support for Pocket PC development (C++ and .NET). ]]> </description>
</item>
<item>
<title>Exploring Secrets of .NET Diagnostics</title>
<link>http://www.dotnetcat.com/news/Debug/id/8652/</link>
<pubDate>Fri, 14 Mar 2008 23:55:33 -0500</pubDate>
<description> <![CDATA[ Instrumenting an application with tracing has become increasingly sophisticated as the .NET framework has matured. Find out how to use tracing in your applications, how to fine-tune tracing to your needs with custom listeners, and how to gain field-level and robust formatting control over the output. ]]> </description>
</item>
<item>
<title>Debugging Memory Related Issues in .Net Application Using WinDBG and SOS</title>
<link>http://www.dotnetcat.com/news/Debug/id/8504/</link>
<pubDate>Tue, 12 Feb 2008 13:33:00 -0600</pubDate>
<description> <![CDATA[ Visual studio inbuilt debugger is a well known debugger, which offers both managed and mixed debugging options but at times when we need to debug memory related issues such as to optimize application performance, solve crashes or out of memory exceptions, then we really need to have a more powerful debugger, that can give detailed insight of objects on heap and GC... ]]> </description>
</item>
<item>
<title>Authoring Visual Studio Debugger Visualizers</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/8432/</link>
<pubDate>Tue, 22 Jan 2008 06:28:00 -0600</pubDate>
<description> <![CDATA[ Visual Studio Debugger Visualizers are a great addition to the developers debugging toolbox. Their purpose is to provide a custom view of data during a debugging session. This article will cover developing a simple string visualizer that allows the string to be replaced during the visualizer session. Additionally, necessary steps to debug your visualizer will be covered.
 ]]> </description>
</item>
<item>
<title>Deadlock Detection in Existing Code</title>
<link>http://www.dotnetcat.com/news/Debug/id/7997/</link>
<pubDate>Tue, 18 Sep 2007 14:36:00 -0500</pubDate>
<description> <![CDATA[ The article briefly discusses deadlocks behavior and presents an easy way to detect them. ]]> </description>
</item>
<item>
<title>Wait Chain Traversal</title>
<link>http://www.dotnetcat.com/news/Debug/id/7592/</link>
<pubDate>Mon, 21 May 2007 19:00:00 -0500</pubDate>
<description> <![CDATA[ Windows Vista has a very interesting new API called Wait Chain Traversal (WCT), which allows you to determine when and why a process is deadlocked. The good news is that WCT will report exactly what synchronization object you are deadlocking on. The bad news is that it only reports a limited set of synchronization primitives. Even with that limitation, it’s still a very useful API and something you’ll want to have in your debugging toolkit.

In this column, I want to discuss the WCT API, its usage, and its limitations. As part of this column, I give you a tool that pinpoints all the deadlocks supported by WCT. Because I insisted on writing the tool in .NET, I also get to show you a descent into the depths of interop despair and how I was able to get the WCT API working from the .NET Framework. ]]> </description>
</item>
<item>
<title>Debugging SQL Server 2005 Stored Procedures in Visual Studio</title>
<link>http://www.dotnetcat.com/news/Database/id/7384/</link>
<pubDate>Tue, 15 May 2007 19:00:00 -0500</pubDate>
<description> <![CDATA[ 
With Microsoft SQL Server 2000 it was possible to debug stored procedures from directly within Query Analyzer (see
Debugging a SQL Stored Procedure from inside SQL Server 2000
Query Analyzer for more information). With SQL Server 2005, however, this functionality was moved out of SQL Server Management
Studio and into the Visual Studio IDE. Using this technique, it is possible to step into your stored procedures, one statement
at a time, from within Visual Studio. It is also possible to set breakpoints within your stored procedures' statements and
have these breakpoints hit when debugging your application.

All editions of SQL Server 2005 include debugging support (including the Express Edition). However, only the Team Systems and Professional
editions of Visual Studio enable stored procedure debugging from within the IDE. In short, if you are using
Visual Web Developer or
Visual Studio Standard Edition then you cannot
step through a stored procedure or enter the stored procedure via application debugging.

In this article we will examine how to debug SQL Server 2005 stored procedures through the Visual Studio IDE. We will
look at both stepping into a stored procedure directly from the IDE as well as how to set breakpoints within the stored
procedure that are then hit when debugging the application.
 ]]> </description>
</item>
<item>
<title>Improve Debugging And Performance Tuning With ETW</title>
<link>http://www.dotnetcat.com/news/Debug/id/6903/</link>
<pubDate>Mon, 12 Mar 2007 19:00:00 -0500</pubDate>
<description> <![CDATA[ Event Tracing for Windows (ETW) provides general-purpose, high-speed tracing of events raised by both user-mode applications and kernel-mode device drivers. Learn how ETW can improve your development and debugging work.
 ]]> </description>
</item>
<item>
<title>NetTrace - A simple, lightweight, fast debugging tracer</title>
<link>http://www.dotnetcat.com/news/Debug/id/6251/</link>
<pubDate>Mon, 18 Dec 2006 15:10:00 -0600</pubDate>
<description> <![CDATA[ An extremely easy to use and incredibly fast tracer with lots of options. ]]> </description>
</item>
<item>
<title>Debug Leaky Apps: Identify And Prevent Memory Leaks In Managed Code</title>
<link>http://www.dotnetcat.com/news/Debug/id/6210/</link>
<pubDate>Tue, 21 Nov 2006 18:00:00 -0600</pubDate>
<description> <![CDATA[ When is the .NET Garbage Collector unable to reclaim memory? The answer might surprise you. Stay tuned. ]]> </description>
</item>
</channel>
</rss> 