<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DeStructUred Blog &#187; debugging</title>
	<atom:link href="http://www.joselise.com/wp/tag/debugging/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joselise.com/wp</link>
	<description>Thoughts about life, technology, productivity, etc.</description>
	<lastBuildDate>Sun, 05 Feb 2012 21:20:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Three Debugging Proxies to decode HTTP and HTTPS streams</title>
		<link>http://www.joselise.com/wp/2007/05/30/three-debugging-proxies-to-decode-http-and-https-streams/</link>
		<comments>http://www.joselise.com/wp/2007/05/30/three-debugging-proxies-to-decode-http-and-https-streams/#comments</comments>
		<pubDate>Wed, 30 May 2007 20:15:33 +0000</pubDate>
		<dc:creator>cjlise</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[debugging]]></category>
		<category><![CDATA[freeware]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[HTTPS]]></category>
		<category><![CDATA[Proxy]]></category>

		<guid isPermaLink="false">http://www.joselise.com/wp/2007/05/30/three-debugging-proxies-to-decode-http-and-https-streams/</guid>
		<description><![CDATA[There are several ways to debug and analyze web applications. The first approach is to use network sniffers like wireshark. The problem with sniffers is that they are not so easy to use, and by default they capture all the network traffic. If the interest is only HTTP streams, it is required to add filters [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"><!--
google_ad_client = "pub-0843350268032642";
google_ad_width = 468;
google_ad_height = 60;
google_ad_format = "468x60_as";
google_ad_type = "text_image";
google_ad_channel ="";
//--></script>
<script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<p>There are several ways to debug and analyze web applications. The first approach is to use network sniffers like <a href="http://www.wireshark.org/">wireshark.</a> The problem with sniffers is that they are not so easy to use, and by default they capture all the network traffic. If the interest is only HTTP streams, it is required to add filters to remove all the information not relevant. Another drawback of sniffer, is that they are useless if the interest is the capture of a HTTPS stream: The sniffer captures the network stream but in crypt ed format. So it is useless. In such situation, a debugging proxy is a more relevant tool: They capture directly the HTTP streams&nbsp;and display directly the captured data without any filtering. Moreover most of them are able to decode HTTPS streams. I use the 3 debugging proxy below:</p>
<ul>
<li><a href="http://www.owasp.org/index.php/OWASP_WebScarab_Project">WebScarab</a>:&nbsp;&nbsp;&quot;WebScarab is a framework for analyzing applications that communicate using the HTTP and HTTPS protocols. It is written in Java, and is thus portable to many platforms. WebScarab has several modes of operation, implemented by a number of plugins. In its most common usage, WebScarab operates as an intercepting proxy, allowing the operator to review and modify requests created by the browser before they are sent to the server, and to review and modify responses returned from the server before they are received by the browser. WebScarab is able to intercept both HTTP and HTTPS communication. The operator can also review the conversations (requests and responses) that have passed through WebScarab.&quot;</li>
<li><a href="http://portswigger.net/proxy/">Burp Proxy</a>: &quot;Burp proxy is an interactive HTTP/S proxy server for attacking and debugging web-enabled applications. It operates as a man-in-the-middle between the end browser and the target web server, and allows the user to intercept, inspect and modify the raw traffic passing in both directions.&quot; Burp Proxy is also written in Java.</li>
<li><a href="http://www.fiddlertool.com/fiddler/">Fiddler</a>: &quot;Fiddler is a HTTP Debugging Proxy which logs all HTTP traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP Traffic, set breakpoints, and &quot;fiddle&quot; with incoming or outgoing data. Fiddler includes a powerful event-based scripting subsystem, and can be extended using any .NET language.&quot;</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.joselise.com/wp/2007/05/30/three-debugging-proxies-to-decode-http-and-https-streams/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Dr Watson debugger round up</title>
		<link>http://www.joselise.com/wp/2007/05/23/dr-watson-debugger-round-up/</link>
		<comments>http://www.joselise.com/wp/2007/05/23/dr-watson-debugger-round-up/#comments</comments>
		<pubDate>Wed, 23 May 2007 20:47:22 +0000</pubDate>
		<dc:creator>cjlise</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[dbg]]></category>
		<category><![CDATA[debugging]]></category>
		<category><![CDATA[dump]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.joselise.com/wp/2007/05/23/dr-watson-debugger-round-up/</guid>
		<description><![CDATA[Today, I wanted to deactivate Dr Watson on my PC (Windows XP-SP2) and it tooks me some time to find the relevant information to do that. The interesting thing is that, I found some very useful information about the debugger: Description of the Dr. Watson for Windows (Drwtsn32.exe) Tool: This article describes the Dr. Watson [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"><!--
google_ad_client = "pub-0843350268032642";
google_ad_width = 468;
google_ad_height = 60;
google_ad_format = "468x60_as";
google_ad_type = "text_image";
google_ad_channel ="";
//--></script>
<script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<p>Today, I wanted to deactivate Dr Watson on my PC (Windows XP-SP2) and it tooks me some time to find the relevant information to do that. The interesting thing is that, I found some very useful information about the debugger:</p>
<ul>
<li><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://support.microsoft.com/kb/308538" target="_blank"><strong>Description of the Dr. Watson for Windows (Drwtsn32.exe) Tool</strong></a><font size="2">: This article describes the Dr. Watson for Windows program error debugger tool included in Windows XP. </font></li>
<p>    <font size="2"></p>
<li><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_overview.mspx" target="_blank"><strong>Microsoft Windows XP &#8211; Dr. Watson overview</strong></a><strong>:</strong> <strong>Dr</strong>. <strong>Watson</strong> for Windows is a program error debugger The information obtained and logged by <strong>Dr</strong>. <strong>Watson</strong> is the information needed by technical support groups <strong>&#8230;</strong></li>
<li><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://support.microsoft.com/kb/188296" target="_blank"><strong>How to disable Dr. Watson for Windows</strong></a>: This article describes how to disable and re-enable the Dr. Watson program.</li>
<li><a href="http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_setup.mspx"><strong>Microsoft Windows XP &#8211; Setting up Dr. Watson</strong></a>: <strong>Dr</strong>. <strong>Watson</strong> (Drwtsn32.exe) is installed in your system folder when you set up Windows. The default options are set the first time <strong>Dr</strong>. <strong>Watson</strong> runs.</li>
<li><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_logfile.mspx" target="_blank"><strong>Microsoft Windows XP &#8211; Using the Dr. Watson log file</strong></a>: When a program error occurs, <strong>Dr</strong>. <strong>Watson gener ates a log file (Drwtsn32.log).</strong> The log file will always start with the following line: Application exception &#8230;</li>
<li><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/app_dr_watson.mspx" target="_blank"><strong>Microsoft Windows XP &#8211; Using Dr. Watson</strong></a><strong>:</strong> Dr. Watson detects information about system and program failures and records the information in a log file In the event of a program error, Dr. Watson &#8230;</li>
<li><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_options.mspx" target="_blank"><strong>Microsoft Windows XP &#8211; Working with Dr. Watson</strong></a><strong>:</strong> You can use the Dr. Watson for Windows dialog box to change the behavior of Dr. Watson. The data that you specify is stored in Registry Editor under the key &#8230;</li>
<p>    </font></ul>
]]></content:encoded>
			<wfw:commentRss>http://www.joselise.com/wp/2007/05/23/dr-watson-debugger-round-up/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Resources to help create a crash dump with ADPlus</title>
		<link>http://www.joselise.com/wp/2006/09/15/resources-to-help-create-a-crash-dump-with-adplus/</link>
		<comments>http://www.joselise.com/wp/2006/09/15/resources-to-help-create-a-crash-dump-with-adplus/#comments</comments>
		<pubDate>Fri, 15 Sep 2006 11:44:14 +0000</pubDate>
		<dc:creator>cjlise</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[crash]]></category>
		<category><![CDATA[dbg]]></category>
		<category><![CDATA[debugging]]></category>
		<category><![CDATA[dump]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[production]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.joselise.com/wp/2006/09/15/resources-to-help-create-a-crash-dump-with-adplus/</guid>
		<description><![CDATA[How to use ADPlus to troubleshoot &#8220;hangs&#8221; and &#8220;crashes&#8221; : Microsoft Technet document describing how to use ADPlus Application debugging in a production environment : Pdf book downloadable from Microsoft Production Debugging for .NET Framework Applications:  Pdf book  more dedicated to .Net  debuggging]]></description>
			<content:encoded><![CDATA[<p><!--adsense--></p>
<ul>
<li><a href="http://www.support.microsoft.com/kb/286350">How to use ADPlus to troubleshoot &#8220;hangs&#8221; and &#8220;crashes&#8221;</a> : Microsoft Technet document describing how to use ADPlus</li>
</ul>
<ul>
<li><a href="http://download.microsoft.com/download/d/f/c/dfc7a022-3426-4868-b23c-3818a6e54305/Application%20Debugging.pdf">Application debugging in a production environment</a> : Pdf book downloadable from Microsoft</li>
</ul>
<ul>
<li><a href="http://www.willydev.net/descargas/prev/DBG_download.pdf">Production Debugging for .NET Framework Applications</a>:  Pdf book  more dedicated to .Net  debuggging</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.joselise.com/wp/2006/09/15/resources-to-help-create-a-crash-dump-with-adplus/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.334 seconds -->

