Sign in
Debugging Toolbox
Windbg scripts, debugging and troubleshooting tools and techniques to help you isolate software problems.
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
About
Email Blog Author
RSS for posts
Atom
RSS for comments
OK
Search
Tags
ASP
Books
Breakpoints
Call Stack
Crash
Disassembly
Exceptions
Hang
Heap Corruption
High CPU
Interview
Just For Fun
Magic Pointers
Memory Leak
Modules
NetWiz Tool
PE Headers
Performance Bottlenecks
Performance Monitor
Personal
PowerDbg Library
PowerDbg Scripts
PowerShell Scripts
Random Thoughts
Read Me
Reporting Services
Serviced Components
SharePoint
Sherlock Tool
Special Commands
SQL Commands
SQL Connections
Stack Corruption
Symbols
Threads
Tracing
Troubleshooting
Windbg Scripts
Archive
Archives
October 2012
(1)
May 2012
(1)
March 2012
(1)
October 2011
(1)
September 2011
(1)
February 2011
(1)
October 2010
(1)
August 2010
(1)
May 2010
(1)
March 2010
(2)
January 2010
(1)
December 2009
(1)
November 2009
(1)
October 2009
(2)
September 2009
(3)
August 2009
(5)
May 2009
(1)
April 2009
(2)
March 2009
(3)
February 2009
(3)
January 2009
(1)
November 2008
(2)
October 2008
(1)
September 2008
(2)
August 2008
(5)
July 2008
(5)
June 2008
(5)
May 2008
(1)
April 2008
(7)
March 2008
(5)
February 2008
(4)
January 2008
(2)
December 2007
(2)
October 2007
(1)
September 2007
(2)
August 2007
(1)
July 2007
(4)
June 2007
(2)
May 2007
(3)
April 2007
(5)
March 2007
(5)
April, 2008
MSDN Blogs
>
Debugging Toolbox
>
April, 2008
Posts
Subscribe via RSS
Sort by:
Most Recent
|
Most Views
|
Most Comments
Excerpt View
|
Full Post View
Debugging Toolbox
Special Command—Extracting Class and Struct Fields Using dt
Posted
over 5 years ago
by
rafarah
1
Comments
dt is another command used almost all the time whenever you want to get the fields and type for a structure or class. For example, you may have a this pointer and use dt to get its fields and type. It’s a simple command with interesting variations...
Debugging Toolbox
Special Command—Use lm* and Get All Details from Modules
Posted
over 5 years ago
by
rafarah
3
Comments
Yet another basic and useful command: lm . Hmmmmm… OK so you already know this command. Great! But do you know all of its variations? Usually when we get used to a command we don’t try to explore its variations and sometimes one of these variations...
Debugging Toolbox
[PowerShell Script] Displaying the Top 5 Exceptions and Up to 5 Different Call Stacks For Each Exception
Posted
over 5 years ago
by
rafarah
9
Comments
During a lab I had about a month ago, one of my colleagues, Tag, whom I had opportunity to mention in a previous post, asked me if I could create a PowerShell script that displays statistics of exceptions, with call stacks included. For me it sounded...
Debugging Toolbox
Special Command—Searching the Call Stack for Symbols or Modules Using !findstack
Posted
over 5 years ago
by
rafarah
1
Comments
During your debugging session, you may find yourself trying to identify if a specific symbol or module appears in one or more threads. There’s more than one way to do that, and here I covert it in the simplest way: !findstack This command accepts...
Debugging Toolbox
My Team is Hiring
Posted
over 5 years ago
by
rafarah
2
Comments
All my posts are provided "AS IS" with no warranties, and confer no rights For PFE Job Opportunities at Microsoft, please visit our website at: http://members.microsoft.com/careers/search/default.aspx - search for keyword “PFE” “PFE: The best place...
Debugging Toolbox
[PowerShell Script] PowerDbg v3.1 - Using PowerShell to Control WinDbg
Posted
over 5 years ago
by
rafarah
5
Comments
This new version has one more parser for !PrintException and a killer feature that my colleagues and myself have wanted since the beginning: PowerDbg, more specifically Send-PowerDbgCommand , which now has the ability to wait until a command finished...
Debugging Toolbox
Comparing RegEx.Replace, String.Replace and StringBuilder.Replace – Which has better performance?
Posted
over 5 years ago
by
rafarah
20
Comments
A few days ago I was with Frank Taglianetti (no links here, he doesn’t have a blog yet), a PFE from my team that I met for the first time at that day while doing a Lab for one of our customers. By Lab I mean stress testing and troubleshooting a customer...
Page 1 of 1 (7 items)