User Tools

Site Tools


debugging_windows

Description

Howto debug someting in this “operating system” This document is intended mainly for linux sysadmins that hate m$ and want to help “Windows Sysadmins” to debug any error on this shit…

Tools

Diving into M$ documentation (tons of it, only a few important words). I found that there are only a few tools available (free and without using hacking tools, which are the next step).

Debug Diagnostic Tool

  • Link at the moment of writing this doc.
  • Link to the “documentation”.

The most Useful thing of this tool is that you can “Attach an Assembler” to ANY process running on the system. It will attach while running but will show information from the process start till the moment you connect and will continue logging information.

Of course, you'll also be able to generate a dump (dump memory of the process), but I HADN'T been able to open this kind of dumps with WINDBG cause you'll have to provide all the libs (like gdb in linux) and don't know why, windows is not able to find by itself (like linux do)… I don't want to waste my time in this part so I go on with the next set of tools.

SysInternals

God save the king: ProcessMonitor (procmon.exe) If you're looking for strace, you're looking for this tool. Start it, add a filter rule (if you don't want to run crazy), for example:

ColumnRelationValueAction
Process NameContainsw3wpInclude

GO! You'll need to save it to a log file (I used CSV) to be able to filter all the noise.

WinDbg

The windows debugger As I told on the DebugDiag tools part, I hadn't been hable to make it work and open a User Dump of an application, but maybe you'll be able to…

CygWin

I can't live with:

  • grep/egrep
  • less
  • vim
  • locate/find

I simply installed cygwin to have a shell.

debugging_windows.txt · Last modified: 2015/04/02 11:51 by dodger