Debugger to Save Output

bichonfrise74 has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Debugger to Save Output by chrestomanci (Priest) on Jun 29, 2011 at 20:57 UTC
I think you are looking for the trace option in the perl debugger. Just start the debugger, type `t` and enter and then run your program. Every line of code that is executed will be printed to screen. It should no be to hard to send a copy of that output to a file. However, can you tell us more about what you are looking to achieve, because if you are trying to profile your code, or create a call graph, there will be much better tools out there for the purpose.	[reply] [d/l]
Re^2: Debugger to Save Output by Anonymous Monk on Jun 30, 2011 at 08:15 UTC
I don't like the debugger :) `perl -d:Trace foo.pl` [download] Devel::Trace, Devel::Trace::More, Devel::TraceCalls, Devel::TraceMethods, Devel::CallTrace	[reply] [d/l]
Re: Debugger to Save Output by bichonfrise74 (Vicar) on Jun 29, 2011 at 22:04 UTC
Yup, that's it. I knew it was possible. I just wanted to see the different internal / external modules that the program will go.	[reply]
Re^2: Debugger to Save Output by planetscape (Chancellor) on Jun 30, 2011 at 08:08 UTC
Personally, I don't like wading through debugger output (maybe because I've done a great deal of it just recently). Perhaps a better option for you, depending on your needs, is something like that mentioned in the following threads: What modules does my code require? Apply a source filter to all modules to be loaded? Which modules does somescript.pl use? Use of %INC ? and etc. (I played with that last one for a while today, in relation to various problems.) HTH, planetscape	[reply]