My take is that there are no other mod_perl debugging interfaces besides Komodo because the wheel doesn't need reinvented.

Another reason is that we usually write tests, so we spend less time in the debugger and/or run debugging sessions on the test environment instead of in an apache process.

But you can use ptkdb to debug mod_perl apps if you need something that weighs less than Komodo.

UPDATE: I just noticed that you "have been doing just print/Dumper", so you might not be aware about how Apache::DB allows you to run the interactive Perl debugger under mod_perl just like regular perl programs.

trwww

You may use ptkdb - Perl/Tk Debugger as a GUI.

The setup is explained here: ptkdb and Interactive mod_perl Debugging.

HTH

Thomas

Thanks for the info. It doesn't necessary have to be a a GUI. I am just unsure about how to debug when I load up a web page and have some input (ie select some items or click on some links etc). I have use perl -d to debug scripts, but never try it when a web page is involved. So, just curious how other people do it

You want Apache::DB.

Put the following in your httpd.conf:

# conditionally load the perl debugger
<IfDefine PERLDB>
  <Perl>
    use Apache::DB ();
    Apache::DB->init;
  </Perl>
  
  <Location />
    PerlInitHandler Apache::DB
  </Location>
</IfDefine>
[download]

Then start apache like so:

/path/to/apache/bin/httpd -X -D PERLDB

Instead of returning to the terminal like it usually does, the perl debugger will start. Then you can browse around your site. Now you can set breakpoints, step through code, inspect variables, or whatever.

The only way I've found to stop the debugger is with kill -9 PID, so you'll need another terminal.

If you are using mp2, there are a couple additional settings you need. See the link above or run perldoc Apache::DB for the details.

Hope this helps,

trwww