<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: putpkt: write failed: Broken pipe</title>
	<atom:link href="http://www.roathe.com/2009/06/putpkt-write-failed-broken-pipe/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.roathe.com/2009/06/putpkt-write-failed-broken-pipe/</link>
	<description>Where the web comes to die...</description>
	<lastBuildDate>Fri, 13 Jan 2012 21:41:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Lane Roathe</title>
		<link>http://www.roathe.com/2009/06/putpkt-write-failed-broken-pipe/comment-page-1/#comment-88</link>
		<dc:creator>Lane Roathe</dc:creator>
		<pubDate>Tue, 09 Feb 2010 08:08:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.roathe.com/?p=14#comment-88</guid>
		<description>Asad,

I am not sure why scrolling a tableview would result in a broken pipe, although in combination with the &quot;sometimes&quot; symptom my first thought is a bad pointer leading to a memory overwrite.

Try turning on Guard Malloc in the run menu; your program will run really slow but it&#039;s likely to find any memory issues.</description>
		<content:encoded><![CDATA[<p>Asad,</p>
<p>I am not sure why scrolling a tableview would result in a broken pipe, although in combination with the &#8220;sometimes&#8221; symptom my first thought is a bad pointer leading to a memory overwrite.</p>
<p>Try turning on Guard Malloc in the run menu; your program will run really slow but it&#8217;s likely to find any memory issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asad</title>
		<link>http://www.roathe.com/2009/06/putpkt-write-failed-broken-pipe/comment-page-1/#comment-82</link>
		<dc:creator>Asad</dc:creator>
		<pubDate>Fri, 29 Jan 2010 13:00:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.roathe.com/?p=14#comment-82</guid>
		<description>Hey All

i am also facing this problem but this problem happened with me in UITableViewCell.
when i am scrolling the table view, not always but sometimes it crashed and displays the above error in degub console.
please help me what may be the reason.</description>
		<content:encoded><![CDATA[<p>Hey All</p>
<p>i am also facing this problem but this problem happened with me in UITableViewCell.<br />
when i am scrolling the table view, not always but sometimes it crashed and displays the above error in degub console.<br />
please help me what may be the reason.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forrest</title>
		<link>http://www.roathe.com/2009/06/putpkt-write-failed-broken-pipe/comment-page-1/#comment-13</link>
		<dc:creator>Forrest</dc:creator>
		<pubDate>Fri, 11 Sep 2009 18:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.roathe.com/?p=14#comment-13</guid>
		<description>Solved! I have been able to reliably avoid this error completely:

1. Before doing a new build, always stop the debugger first.
2. Then stop the app on the device.
3. Only after doing the above 2 steps, then build and go.

That&#039;s all you need. (No need to restart Xcode, restart device, delete app from device, etc.)

Forrest

PS. This is bug in XCode.</description>
		<content:encoded><![CDATA[<p>Solved! I have been able to reliably avoid this error completely:</p>
<p>1. Before doing a new build, always stop the debugger first.<br />
2. Then stop the app on the device.<br />
3. Only after doing the above 2 steps, then build and go.</p>
<p>That&#8217;s all you need. (No need to restart Xcode, restart device, delete app from device, etc.)</p>
<p>Forrest</p>
<p>PS. This is bug in XCode.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://www.roathe.com/2009/06/putpkt-write-failed-broken-pipe/comment-page-1/#comment-12</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Sun, 09 Aug 2009 02:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.roathe.com/?p=14#comment-12</guid>
		<description>I&#039;m afraid I spoke too soon.  It did help, but only for one program run.  There is something else going on here.</description>
		<content:encoded><![CDATA[<p>I&#8217;m afraid I spoke too soon.  It did help, but only for one program run.  There is something else going on here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://www.roathe.com/2009/06/putpkt-write-failed-broken-pipe/comment-page-1/#comment-11</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Sun, 09 Aug 2009 02:03:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.roathe.com/?p=14#comment-11</guid>
		<description>you saved me all sorts of time and frustration.  thanks for putting the tip out there.</description>
		<content:encoded><![CDATA[<p>you saved me all sorts of time and frustration.  thanks for putting the tip out there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

