in reply to Monitor file require/use

nice script, seems useful (untested so far).

For my current problem, I could use a modifikation, that has the same function, but watches a cgi-script.
As this is done by request of an external browser and executed by the local apache server,
do you think, that your script would serve as a wrapper, and print out loaded files
*and* variables and values being exchanged between them?

That all together would be *very* helpful for both developing and debugging purposes!
--
there are no silly questions killerhippy

Replies are listed 'Best First'.
Re: Re: Monitor file require/use
by bikeNomad (Priest) on Jul 27, 2001 at 17:52 UTC
    What do you mean "print out loaded files *and* variables and values being exchanged between them"? What variables? How do your required or used files exchange values with variables?

    This script uses the debugger interface. If you want to monitor a variable, you can tie it (see perltie and Tie::Scalar or Tie::Array or Tie::Hash). I'm not sure what problem you're trying to solve.

    If you just want to watch a particular CGI, just use a remote debugger like Devel::ptkdb or ActiveState's debugger.

[reply]
      What I am dreaming of ;-) is an omnipotent debuggertool.
      As I only know perl -d so far, I can't imagine a convenient
      way of debugging a cgi-script with multifunctions in depth.
      So I would appreciate a tool telling me that the
      script.pl is currently calling module.pm passing
      variable with value to it      .
      The problem is, that the script.pl is invoked by Apache by browserrequest, so how can you get into that???
      --
      there are no silly questions
      killerhippy
[reply]
        If you want to debug a CGI, look at Devel::ptkdb, which will open a Tk debugger for you. You can set breakpoints on specific lines as needed, possibly with conditions.

        Beyond that, note that "scripts" don't call modules. They require or use modules (which is what my debugger script catches); they call subroutines/methods that were defined by the modules.

[reply]

In Section Code Catacombs