Changes

Jump to navigation Jump to search
Line 130: Line 130:  
[[Debugging CGI programs on live production servers can seriously impair performance. You have been warned !!]]
 
[[Debugging CGI programs on live production servers can seriously impair performance. You have been warned !!]]
   −
I have not tested this as yet. Please see here for further details:
+
Please see here for further details:
    
http://docs.komodoide.com/Manual/debugperl#debugging-perl-komodo-ide-only_configuring-perl-for-cgi-debugging
 
http://docs.komodoide.com/Manual/debugperl#debugging-perl-komodo-ide-only_configuring-perl-for-cgi-debugging
   −
You would need a custom httpd.conf frgament with the following (I am not going to go into the full how to here)
+
You would need a custom httpd.conf fragment. I used 46PerlDebug with these options (configure to suit)
   −
  SetEnv PERL5LIB "/opt/dbgp/perllib"
+
  SetEnv PERL5LIB "/opt/dbgp/perllib:$PERL5LIB"
  SetEnv PERLDB_OPTS "RemotePort=<hostname>:<port>"
+
  SetEnv PERLDB_OPTS "RemotePort=192.168.x.x async=1"
  SetEnv DBGP_IDEKEY "<ide_key>"
+
  SetEnv DBGP_IDEKEY "user"
   −
You should now be able access your cgi-script - e.g. server-manager and debug accordingly.
+
You should now be able access your cgi-script and debug accordingly.
    +
However, having tried it you cannot use this on server-manager panels because perl is setuid.
 +
 +
It could be used in other scenarios, but not server-manager.
    
====Multiple machine debug proxy====
 
====Multiple machine debug proxy====

Navigation menu