From: Jan P. <jp...@us...> - 2006-12-03 12:58:23
|
Update of /cvsroot/e-p-i-c/org.epic.doc/guide In directory sc8-pr-cvs5.sourceforge.net:/tmp/cvs-serv27918/guide Modified Files: guide.xml Log Message: Updated section on the "Perl Remote" launch configuration. Index: guide.xml =================================================================== RCS file: /cvsroot/e-p-i-c/org.epic.doc/guide/guide.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -d -r1.6 -r1.7 --- guide.xml 8 Oct 2006 10:29:22 -0000 1.6 +++ guide.xml 3 Dec 2006 12:58:19 -0000 1.7 @@ -1887,29 +1887,33 @@ <itemizedlist> <listitem> - <para>You need a Perl interpreter installed on your target - machine.</para> + <para>You need a Perl interpreter installed on the remote + host.</para> </listitem> <listitem> - <para>The EPIC debugger opens a network connection between local - and remote host (port number can be specified in the corresponding - launch configuration). So have a look at your firewall - configuration.</para> + <para>During debugging the remote host connects to the local + (Eclipse) host using three TCP ports: the debugger port, the + stdout/stdin port and the stderr port. The debugger port is + specified statically in the launch configuration (see below). The + two other ports are picked up from the range 5000-10000. (EPIC + attempts to reserve these ports in ascending order starting with + 5000.) Make sure that your firewall does not block these required + connections.</para> </listitem> <listitem> <para>Scripts executed and code shown are from different sources: - EPIC displays the code present on your local machine and executes - a copy of this code on the remote host. So if you make changes + EPIC displays the code present on your local host and executes a + copy of this code on the remote host. So if you make changes within your project please make sure to transfer these changes to the remote host (see below for further details).</para> <para>This problem gets more significant for code/modules provided by your Perl installation. If modules on your local and remote - machine differ, debugging results may be quite meaningless. So try - to have the same Perl version installed on both machines and make - sure all modules you require (and are not part of your Eclipse + host differ, debugging results may be quite meaningless. So try to + have the same Perl version installed on both hosts and make sure + all modules you require (which are not part of your Eclipse project) are identical.</para> </listitem> @@ -1918,7 +1922,8 @@ directories within your project or directories that are linked into your projects, EPIC will include these modules in the list of files to be copied to the remote host and adjust the @INC-path for - your remote machine accordingly.</para> + your remote host accordingly. Overall, it is best to set up + project-relative @INC paths in the project properties.</para> </listitem> </itemizedlist> @@ -1972,43 +1977,45 @@ <listitem> <para><guilabel>Local Host IP</guilabel>: this is the IP-address - used by the remote host to connect to your local machine. In most + used by the remote host to connect to your local host. In most cases the default value is appropriate.</para> </listitem> <listitem> <para><guilabel>Target Host Project Installation Path</guilabel>: - the location on the remote machine, where your Eclipse project - should be copied to.</para> + the project's location on the remote host. Make sure that your + Eclipse project can be found at this location.</para> </listitem> <listitem> - <para><guilabel>Port</guilabel>: Port used to transfer data - between local and remote host.</para> + <para><guilabel>Port</guilabel>: Port used by the remote debugger + to connect to the local host.</para> </listitem> <listitem> <para><guilabel>Create Debug Package</guilabel>: if checked, a ZIP - file containing all data to be transfered to the remote machine is - created. This file is stored at the location indicated in + file containing the project files to be transfered to the remote + host is created. This file is stored at the location indicated in <guilabel>Debug Package File Path</guilabel>.</para> </listitem> <listitem> - <para>Press the <guibutton>Debug</guibutton> button.</para> + <para>Press the <guibutton>Debug</guibutton> button. At this + point, the local host starts listening for a remote debugger + connection.</para> </listitem> <listitem> - <para>Extract the ZIP file to the location on your remote machine + <para>Extract the ZIP file to the location on your remote host indicated in <guilabel>Target Host Project Installation Path</guilabel>.</para> </listitem> <listitem> <para>Start the script <command>start_epicDB.pl</command> on your - remote machine (it is located in the directory indicated by - <guilabel>Target Host Project Installation - Path</guilabel>).</para> + remote host (it is included in the ZIP archive and thus located in + the project directory after extraction). This script starts the + debugger and makes it connect to the local host.</para> </listitem> <listitem> |