<?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: Launch Time</title>
	<atom:link href="http://winpdb.org/docs/launch-time/feed/" rel="self" type="application/rss+xml" />
	<link>http://winpdb.org</link>
	<description></description>
	<pubDate>Sat, 04 Feb 2012 22:03:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: fonzy</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-126841</link>
		<dc:creator>fonzy</dc:creator>
		<pubDate>Wed, 20 Oct 2010 11:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-126841</guid>
		<description>When I try to do remote debugging, I get no connection. I start the script on an internal web server, so the necessary ports should be open, and the script waits at the position where I import rpdb2 and start the debugger with a hardcoded password.
But when I enter the hosts IP-adress in my local Winpdb-GUI, no script shows up although the right password was set.

What am I doing wrong? Thanks for help.</description>
		<content:encoded><![CDATA[<p>When I try to do remote debugging, I get no connection. I start the script on an internal web server, so the necessary ports should be open, and the script waits at the position where I import rpdb2 and start the debugger with a hardcoded password.<br />
But when I enter the hosts IP-adress in my local Winpdb-GUI, no script shows up although the right password was set.</p>
<p>What am I doing wrong? Thanks for help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nir</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-104103</link>
		<dc:creator>nir</dc:creator>
		<pubDate>Wed, 06 Jan 2010 20:10:46 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-104103</guid>
		<description>yes, look at the timeout argument</description>
		<content:encoded><![CDATA[<p>yes, look at the timeout argument</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-104001</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Tue, 05 Jan 2010 15:14:02 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-104001</guid>
		<description>Is there a way to launch rpdb2 allowing remote connections, but have it start the script without waiting for a debugger console to attach and say 'go'?</description>
		<content:encoded><![CDATA[<p>Is there a way to launch rpdb2 allowing remote connections, but have it start the script without waiting for a debugger console to attach and say &#8216;go&#8217;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: araud</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-102031</link>
		<dc:creator>araud</dc:creator>
		<pubDate>Tue, 15 Dec 2009 13:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-102031</guid>
		<description>Did anyone managed to attach to local process from console?

I am under windows trying this scenario:
c:/temp/test.py contains:
    import rpdb2; rpdb2.start_embedded_debugger("123")
I run it by double-clicking.
A can attach manually thru gui. But can't get command line working:
    winpdb --attach=test.py --pwd=123 --host=127.0.0.1

All I receive in return is help message...

Thank you!</description>
		<content:encoded><![CDATA[<p>Did anyone managed to attach to local process from console?</p>
<p>I am under windows trying this scenario:<br />
c:/temp/test.py contains:<br />
    import rpdb2; rpdb2.start_embedded_debugger(&#8221;123&#8243;)<br />
I run it by double-clicking.<br />
A can attach manually thru gui. But can&#8217;t get command line working:<br />
    winpdb &#8211;attach=test.py &#8211;pwd=123 &#8211;host=127.0.0.1</p>
<p>All I receive in return is help message&#8230;</p>
<p>Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DKW</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-46776</link>
		<dc:creator>DKW</dc:creator>
		<pubDate>Fri, 05 Dec 2008 15:23:11 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-46776</guid>
		<description>I created a batch file, so I just type "debug" and it launches winpdb with my app loaded.  I find the process of repeatedly navigating through directories to attach to the source code for MY app to be annoying, and this allows me to skip it.</description>
		<content:encoded><![CDATA[<p>I created a batch file, so I just type &#8220;debug&#8221; and it launches winpdb with my app loaded.  I find the process of repeatedly navigating through directories to attach to the source code for MY app to be annoying, and this allows me to skip it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nir</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-33921</link>
		<dc:creator>nir</dc:creator>
		<pubDate>Wed, 17 Sep 2008 07:02:21 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-33921</guid>
		<description>DKW, you are correct that the instructions could be clearer for Windows users. However it is such a nuisance typing the path to the scripts folder that I guess most Windows users start Winpdb from the Start menu.</description>
		<content:encoded><![CDATA[<p>DKW, you are correct that the instructions could be clearer for Windows users. However it is such a nuisance typing the path to the scripts folder that I guess most Windows users start Winpdb from the Start menu.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DKW</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-33833</link>
		<dc:creator>DKW</dc:creator>
		<pubDate>Tue, 16 Sep 2008 16:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-33833</guid>
		<description>I agree with "rak" that these instructions could be clearer how to start up on platforms other than Linux.

On Windows, the following works for me:

python "(path to your Python directory)\Scripts\winpdb_.pyw"  arg1 arg2 arg3 ...

(The quotes are necessary for me because I have a space in my python path.)</description>
		<content:encoded><![CDATA[<p>I agree with &#8220;rak&#8221; that these instructions could be clearer how to start up on platforms other than Linux.</p>
<p>On Windows, the following works for me:</p>
<p>python &#8220;(path to your Python directory)\Scripts\winpdb_.pyw&#8221;  arg1 arg2 arg3 &#8230;</p>
<p>(The quotes are necessary for me because I have a space in my python path.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nir</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-11511</link>
		<dc:creator>nir</dc:creator>
		<pubDate>Sun, 18 May 2008 13:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-11511</guid>
		<description>It is cross platform. What platform are you using?</description>
		<content:encoded><![CDATA[<p>It is cross platform. What platform are you using?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rak</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-11328</link>
		<dc:creator>rak</dc:creator>
		<pubDate>Fri, 16 May 2008 19:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-11328</guid>
		<description>I thought this thing was cross-platform.  Where are the instructions for other platforms?</description>
		<content:encoded><![CDATA[<p>I thought this thing was cross-platform.  Where are the instructions for other platforms?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://winpdb.org/docs/launch-time/comment-page-1/#comment-3583</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 17 Nov 2007 06:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?page_id=8#comment-3583</guid>
		<description>Prevent the debugger from trying to start a new terminal with the -d command line flag.

The -d command line flag makes the debugger start as a server (debugged script) and wait for clients to attach (debugger consoles).

If you do not use the -d flag the debugger starts a client (debugger console) and tries to launch a server (debugged script process) and attach.

If you want to allow connections from remote machines add the -r command line flag.</description>
		<content:encoded><![CDATA[<p>Prevent the debugger from trying to start a new terminal with the -d command line flag.</p>
<p>The -d command line flag makes the debugger start as a server (debugged script) and wait for clients to attach (debugger consoles).</p>
<p>If you do not use the -d flag the debugger starts a client (debugger console) and tries to launch a server (debugged script process) and attach.</p>
<p>If you want to allow connections from remote machines add the -r command line flag.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

