Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
I set up a Perl Remote debug configuration, then run it. An error message is shown: "'Launching RemoteTest' has encountered a problem. An internal error occurred during: 'Launching RemoteTest"", Looking at the error details, it shows 'java.lang.NullPointerException". Do you have any idea where I may make mistakes?
This is my simple procedure:
- In 'remote Systems explorer perspective', create remote project by right click the folder in: /home/CCCHAN3_P/prac/perlPrac/bookPrac
- import files from Remote file system: only have one file called nuFreq.pl which contains only two lines:
- Create a Perl Remote Bug Configuration. The following is the Debug configuration I put in:
File to execute: nuFreq.pl
Local Host IP: 10.212.31.109 (It is the default)
Target Host Project Installation Path: /home/CCCHAN3_P/prac/perlPrac/bookPrac
Port: 5000 (it's the default)
Create Debug Package: unchecked
- Then run it.
Thanks in advance!!
EPIC has no support for loading files located in remote file systems. Even when using a remote debug configuration the files must be contained in a local project.
Hmhm… then… when will the remote debug configuration be usefully used? Thanks.
The current idea is that you maintain a mirror copy of your project on a remote server and in the local file system. Then you can use the remote debug configuration to break in or step through in the remote code. I think the approach is described in the user guide. It's not convenient, but it works (at least for some) and it can also be used to debug mod_perl.