On Wed, Sep 01, 2010 at 12:07:49PM +0100, Dave Page wrote: > Dear Tim, > > I'm wondering if you can help me. I have a problem with analysing a > complicated codebase, and I'm trying to work out whether Devel::NYTProf > is the right tool to use. > > What I'd like to do is trace the execution of a program through a script > and a complex, interdependent series of modules. I'm not able to alter > the codebase to include stack dump debug statements etc. > > Devel::Trace is almost what I want, since it traces statement execution > through files, but it doesn't tell me which subs and methods in each > file are being invoked.
Well, it does in the report generated at the end, but not at the time. > Devel::NYTProf seems to contain this information, but I'm having > difficulty getting it out; using nytprofcg and kcachegrind lets me click > through an execution trace but that's not much more than I get with > ctags. Also, kcachegrind only shows subs that have a certain minimum > execution threshold. > > I've looked at parsing the NYTProf output with Devel::NYTProf::Data but > the methods currently provided don't seem to give me the information I > require, and the documentation warns me not to go poking inside data > structures. > > Do you think I'm barking up the wrong tree trying to use Devel::NYTProf > for this purpose? You've not spelled out what you want clearly enough for me to be sure how to answer your question. What is it you're really looking for. What would it look like? > If so, do you know of any other things I could be using instead? Take a look at http://search.cpan.org/perldoc?Devel::STrace and http://search.cpan.org/perldoc?Debug::Trace and http://search.cpan.org/perldoc?Devel::Trace::More etc. Tim. -- You've received this message because you are subscribed to the Devel::NYTProf Development User group. Group hosted at: http://groups.google.com/group/develnytprof-dev Project hosted at: http://perl-devel-nytprof.googlecode.com CPAN distribution: http://search.cpan.org/dist/Devel-NYTProf To post, email: [email protected] To unsubscribe, email: [email protected]
