http://www.perlmonks.org?node_id=955047

bimleshsharma has asked for the wisdom of the Perl Monks concerning the following question:

for example:
* installed clipse with EPIC at local winXP box.
* Script file is available at other linux box.
* If i run this script at Linux box at same place then working fine.
* The same thing i am trying to debug that script from my local XP box. But not sure what configuration is required. * When i try to run error is saying "module not found" .
* It seems, that script is trying to run locally that is why used module is not including or i need to give path of that remote file so that during debug it will include all module. pls help.

Replies are listed 'Best First'.
Re: How to remote debug perl script usip EPIC tool of eclipse.?
by Perlbotics (Archbishop) on Feb 20, 2012 at 12:05 UTC

    It has been a long time since I used Eclipse/EPIC and I didn't try to remote debug a Perl script. However, the documentation says it's possible: 6.2.3 Perl Remote: Debug a Perl Script on a Remote Machine (PDF)

    What goes wrong when following the steps described in chapter 6.2.3?

    Main obstacles:

    • firewalls (personal- and network-) could block the remote connection (ports 5000-10000)
    • insufficient permissions to run the debug server at the remotelocal host (WinXP)
    • forgetting to run start_epicDB.pl at the remote host (linux)

    I cannot decode your last question, sorry. I read it as Remote Perl program requires modules/libraries that are not available for Win-XP, thus remote debugging is required..

    Update: This quote from the docs might be relevant:

    If modules on your local and remote 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.

Re: How to remote debug perl script usip EPIC tool of eclipse.?
by Khen1950fx (Canon) on Feb 20, 2012 at 12:16 UTC
Re: How to remote debug perl script usip EPIC tool of eclipse.?
by chrestomanci (Priest) on Feb 21, 2012 at 08:49 UTC

    My experience with debugging perl via EPIC has not been that positive. In general I have found that EPIC works well for simple scripts and demos, but if you attempt to debug something complex such a Catalyst application with it's very deep stack, or a DBIx::Class or Moose application with a complex and deeply inherited class structure, the whole thing grinds to a halt, and you frequently have to kill perl processes, and eclipse.

    On the basis of that, my advice would be to learn how to use the perl command line debugger and debug over an SSH console session. If you must use a GUI debugger, then you could use the ptkdb debugger over an X11 session, but I don't recommend it.

      IMHO no X11 session is needed just portforwardings. The builtin editor/gui support works via that interface.

      Though i never tried it myself.

      Cheers Rolf