<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Matasano Chargen - Latest Comments in Debug Windows Service Startup Without Using gflags</title><link>http://matasanochargen.disqus.com/</link><description></description><language>en</language><lastBuildDate>Tue, 07 Jul 2009 05:26:17 -0000</lastBuildDate><item><title>Re: Debug Windows Service Startup Without Using gflags</title><link>http://www.matasano.com/log/617/debug-windows-service-startup-without-using-gflags/#comment-12245030</link><description>I also think that you should follow step 2.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fitstiks</dc:creator><pubDate>Tue, 07 Jul 2009 05:26:17 -0000</pubDate></item><item><title>Re: Debug Windows Service Startup Without Using gflags</title><link>http://www.matasano.com/log/617/debug-windows-service-startup-without-using-gflags/#comment-2321126</link><description>Alternatively, you could follow step 2 and then download PEBrowse Interactive from my website, &lt;a href="http://www.smidgeonsoft.com" rel="nofollow"&gt;www.smidgeonsoft.com&lt;/a&gt;.  From File/IFEO Manager, add the service -- this uses the registry key, Image File Execution Options and launches PEBrowse when the service starts.  Then under Tools/Configure/Debug, check the option, "Break on Process Initialization".  When the service starts, this will stop the process and bring up the debugger when the service is first loaded.  This allows one to debug the service without munging the executable with an INT 3 and even debug the loader and any DLLs startup code.  Or, you can read the documentation page on my website for how to debug ASP.NET pages which essentially uses the same technique.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Russ Osterlund</dc:creator><pubDate>Mon, 27 Nov 2006 11:03:09 -0000</pubDate></item></channel></rss>