gabts wrote on Mon Feb 7 18:54:59 CET 2005:
Hi, I'm trying to debug a Perl/CGI web application with eclipse/EPIC. Problem 1: The application does not have a startup html file, but starts with a .pl file instead. How do I do this in EPIC? (I found a workaround by creating a dummy html file with a link to the perl script, but what is the true way to do this?) Problem 2: When I start debugging with "Run -> Debug...", some other file from my application is displayed in the browser window althoung I enterd my dummy html file (see problem 1) in "HTML Startup File:". Only when I start a second debug process, the intended html file is displayed. Any hints? Problem 3: After setting a breakpoint to the first instruction and clicking the link to my perl script, the debugger does not stop and the browser window waits forever. What's going wrong here? Thanks in advance for any comments, Tom [Eclipse 3.0, EPIC Debug Plugin 0.2.0, ActivePerl 5.8.4, Win2K]
ndzou wrote on Thu Feb 10 00:29:34 CET 2005:
I'm also having the same problem, the Perl process seems to hang while processing a CGI page. If I take that Perl command line and run it in a DOS prompt window, then the debugger starts with the DB<1> prompt. My Setup is Windows XP/ActivePerl 188.8.131.520 (with the sf Padwalker)/Eclipse 3.1M4/EPIC 0.3.10
pacanukeha wrote on Tue Aug 30 19:43:03 MEST 2005:
Eclipse 3.1/EPIC 0.3.11 from updates/testing/ActiveState 5.8.7/Padwalker from EPIC site/ xampplite I have numerous problems - When trying to debug CGI I get the following in my error log: !MESSAGE (CGI-Target)Could not connect to CGI-Proxy For regular debugging I get: !MESSAGE An internal error occurred during: "Initialize Debug View". !STACK 0 java.lang.NullPointerException at org.eclipse.debug.internal.ui.views.launch.LaunchView.findFrame(LaunchView.java:454) at org.eclipse.debug.internal.ui.views.launch.LaunchView.access$5(LaunchView.java:446) at org.eclipse.debug.internal.ui.views.launch.LaunchView$3.run(LaunchView.java:420) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) Along with an EPIG Error (heh) asking me to install Padwalker even though I unzipped the contents into the perl/bin directory.
stephan_ruehl wrote on Thu Feb 10 18:48:11 CET 2005:
Hi Tom, Problem 1: at the moment it is the only possibility. But I already made same changes to the debugger to allow for selecting Perl files as startup files if they reside in the CGI Root Directory (just point HTML Startup File to the Perl file and HTML Root Directory to CGI Root Directory). This feature will be available in the next testing release. Problem 2: can you reproduce this behavior with the current testing version ? I could not reproduce it on my machine. Which browser do you use ? Problem 3: same as as problem 2. If the problem remains could you send me the files ? Stephan
pacanukeha wrote on Tue Aug 30 19:56:30 MEST 2005:
Note - after RTFM and putting padwalker in the right place the PW error goes away, the others are still there.
Note: The above is an archived snapshot of a forum thread. Use the original thread at sf.net to post comments.