-
-
Notifications
You must be signed in to change notification settings - Fork 75
Help: How to debug perl script from browser #2127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
There is no high-level way to debug a scripts opened in browser. You should configure remote debugging for that manually. |
I tried the remote debugging but still don't really know how to configure everything. PhpStorm listens on 0.0.0.0:12345 but now I'm stuck. |
Probably this issue will help #1771 |
@hurricup I got it working! Finally! 🎉 Let me document it here even though the wiki would be a better place. Setup IDE like this:
Setup nginx like this (port must match with IDE port):
Then click "Debug..." in IDE in order to start listening and then open the perl script in the browser. The key for me was not to set the environment variables in my home directory but right in the browser config and then change the Shebang. Problem solved! |
referenced in documentation. thanks. |
Uh oh!
There was an error while loading. Please reload this page.
sudo cpan Devel::Camelcadedb
I browsed through the wiki (https://github.com/Camelcade/Perl5-IDEA/wiki/Perl-Debugger) and all the issues that are related to debugging and couldn't find anything helpful on how to setup browser debugging. Debugging within the IDE works fine but I have no idea how to configure my system in order to call
http://localhost/cgi-bin/test.cgi
and debug the test script which looks like this:I use nginx with fcgiwrap and the following config:
The script is executed without problems and I can see "Hi" in my browser.
What do I need to do in order to debug this script when called from the browser? This is just a test script but later on I want to debug a whole perl application.
The text was updated successfully, but these errors were encountered: