Channels ▼
RSS

Tools

Introduction to Power Debugging


Previously in the Advanced Products research group at Citrix Systems, Toby is currently working in Processor Enabling at Intel Corporation. He can be contacted at toby@opferman.com.

The debugger is one of the simplest tools available to a developer and yet it is also one of the most powerful. In the simplest case the debugger can display a stack trace of a thread and set break points on functions. This simply requires the debugger to walk the stack or modify and restore memory locations. The outcome of these simple actions can be very powerful. The use of one or two simple commands can solve what would otherwise be a head banging problem.

Developers may spend hours modifying source code to help track down the problems they are seeing. This is definitely a good thing to do and is often necessary, however there are tricks and shortcuts that can be done just using the debugger.

In this article, I will not be covering how to do stack traces or how to track down an access violation. Instead I will show how to use the debugger in non-conventional ways and demonstrate advanced debugging and reverse engineering techniques using very simple debugger features.

The tools I will be using in this article are "cdb", "ntsd" and "windbg," which are freely downloadable debuggers provided by Microsoft (http://www.microsoft.com/whdc/devtools/ddk/default.mspx). There are obviously many other great tools and debuggers such as Bounds Checker, Softice, Ollydebug, VTune and etc. however these are beyond the scope of what will be covered here.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video