On Thu, Jan 15, 2009 at 03:29:36PM -0500, Ryan Duval wrote: > Hi Tim. First off, great job. I apologize if this has been answered > elsewhere but I feel I've done due diligence in trying to look it > up myself. > > What I'm trying to get is an execution tree for a script. I've > heard it called many things (call tree/graph, execution tree/graph) > but in English it is some kind of output for the order in which > subroutines are executed.
Why, exactly? > It seems like a great thing for your module to provide, something along the > lines of what you'd get with DProf/dprofpp: > > $ dprofpp -t tmon.out | grep 'main::' > > This was my approach at first but I know that DProf is flawed. Not > sure if it would affect the subroutine call tree output (dprofpp > -t) but regardless, NYTProf is the future. :-) > A colleague then suggested I work with the raw NYT output. I set > compress=0 but the database file appeared to still be in some > format. I then discovered ReadStream.pm and read the POD. After > playing around a bit, none of the tags seem to contain information > for determining the order that subs were executed. Is this > available at all? Not currently, though it could be added. > Thanks for your help. Who knows, I may contribute something if it's > possible. Might be time for my first CPAN module! The sub profiler (pp_entersub_profiler() etc) is currently memory-only. You'd need to patch it to emit data to the profile file like the statement profiler (DB_stmt() etc) does. If you're interested in contributing to this work then join the mailing list (http://groups.google.com/group/develnytprof-dev) and I'll guide you. 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] -~----------~----~----~----~------~----~------~--~---
