/ 
Devel-TraceUse-2.04
River stage one • 3 direct dependents • 3 total dependents
/ Devel::TraceUse

NAME

Devel::TraceUse - show the modules your program loads, recursively

SYNOPSIS

An apparently simple program may load a lot of modules. That's useful, but sometimes you may wonder exactly which part of your program loads which module.

Devel::TraceUse can analyze a program to see which part used which module. I recommend using it from the command line:

$ perl -d:TraceUse your_program.pl

This will display a tree of the modules ultimately used to run your program. (It also runs your program with only a little startup cost all the way through to the end.)

Modules used from your_program.pl:
   1.  strict 1.04, your_program.pl line 1 [main]
   2.  warnings 1.06, your_program.pl line 2 [main]
   3.  Getopt::Long 2.37, your_program.pl line 3 [main]
   4.    vars 1.01, Getopt/Long.pm line 37
   5.      warnings::register 1.01, vars.pm line 7
   6.    Exporter 5.62, Getopt/Long.pm line 43
   9.      Exporter::Heavy 5.62, Exporter.pm line 18
   7.    constant 1.13, Getopt/Long.pm line 226
   8.    overload 1.06, Getopt/Long.pm line 1487 [Getopt::Long::CallBack]

The load order is listed on the first column. The version is displayed after the module name, if available. The calling package is shown between square brackets if different from the package that can be inferred from the file name. Extra information is also provided if the module was loaded from within and eval.

Devel::TraceUse will also report modules that failed to be loaded, under the modules that tried to load them.

In the very rare case when Devel::TraceUse is not able to attach a loaded module to the tree, it will be reported at the end.

Even though using -MDevel::TraceUse is possible, it is preferable to use -d:TraceUse, as the debugger will provide more accurate information in the case of eval.

Parameters

You can hide the core modules that your program used by providing the hidecore argument:

$ perl -d:TraceUse=hidecore your_program.pl

This will not renumber the modules so the core module's positions will be visible as gaps in the numbering. In some cases evidence may also be visible of the core module's usage (e.g. a caller shown as base or parent).

You may also specify the version of Perl for which you want to hide the core modules (the default is the running version):

$ perl -d:TraceUse=hidecore:5.8.1 your_program.pl

The version string can be given as x.yyy.zzz (dot-separated) or x.yyyzzz (decimal). For example, the strings 5.8.1, 5.08.01, 5.008.001 and 5.008001 will all represent Perl version 5.8.1, and 5.5.30, 5.005_03 will all represent Perl version 5.005_03.

AUTHORS

chromatic, <chromatic at wgz.org>

Philippe Bruhat, <book at cpan.org>

Contributors

hidecore option contributed by David Leadbeater, <dgl@dgl.cx>.

BUGS

Please report any bugs or feature requests to bug-devel-traceuse at rt.cpan.org, or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Devel-TraceUse. We can both track it there.

SUPPORT

You can find documentation for this module with the perldoc command.

perldoc Devel::TraceUse

You can also look for information at:

COPYRIGHT

Copyright 2006 chromatic, most rights reserved.

Copyright 2010 Philippe Bruhat (BooK), for the rewrite.

LICENSE

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.