Re: Profiling via prove?

prove is just a Perl script - you can debug it like any other Perl script. You should be able to do something like:

perl -d `which prove` -j4
[download]

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

Comment on Re: Profiling via prove? Select or Download Code

Replies are listed 'Best First'.
Re^2: Profiling via prove? by kyoob (Initiate) on Jan 24, 2014 at 17:43 UTC
Windows doesn't like it. I've tried a few flavors of that: '`perl -d:SmallProf prove -r -j4`' got me '`Can't open perl script "prove": No such file or directory`' I tried the full path to the app, '`perl -d:SmallProf C:\Perl64\lib\App\prove.pm -r -j4`' and get a blank newline then a return to my command line. (Well, the first time it told me to fix a deprecated '`defined(@array)`' call in `Devel::SmallProf`, but whatevs). Note that `prove` runs fine on this machine otherwise, aside from this parallel processing weirdness. Is there a way to pass perl arguments to `prove` via the app's '`::`' argument passer gadget? This is Perl 5.16.1 built for MSWin32-x64-multi-thread, running on Windows 7 Pro, 64-bit OS.	[reply] [d/l] [select]
Re^3: Profiling via prove? by kyoob (Initiate) on Jan 24, 2014 at 18:20 UTC
Eureka, thanks to ilmari_ in #perl-help. In the end I needed to set `PERL5OPTS` to '`-d:SmallProf`` and run `prove` normally. Got the same run with the same issues I'd been saying, along with a big whopping profiler output.	[reply] [d/l] [select]