On Wed, Jul 15, 2009 at 07:54:11PM -0500, Elliot Shank wrote: > > Tim Bunce wrote: > > A stacktrace would be a big help. > > Below. Don't know that it will be any use. Grabbed via VS 2005; > given that this is Strawberry, no surprise that it's not able to > understand any GCC information, so all we've got is addresses.
> This was done with Subversion r812. I tried r813-r828 and got big failures > in t/test16.t. That's probably not a problem. I tend to develop NYTProf with perl5.8 so test16, which needs 5.9, gets left behind. I'll update it now. [...] Done (r832). Fixed a bunch of compiler warnings re printf args for the logging as well. > As you'll see from the logs, in this case I tried profiling "perl > Build.PL" for our custom Module::Build subclass' distro. Modules that > the distro "use"s and their installed versions: If you grep the log for ^New you'll see that it doesn't load in many modules before it crashes. Looks like it only got to line 9 of Build.PL and line 12 of Custom/Module/Build.pm, before finally dieing in strict::unimport called from Fatal::_make_fatal. So it seems likely that autodie is involved. Could you try to cut that down to an as-small-as-possible testcase? > > If the fault is reproducible with blocks=0 then use that as it'll run > > faster and produce a less noisy log. > > http://galumph.com/transfer/nytprof.trace.blocks=0.log.gz (20K) I see from the log that you're getting 0's for all the timings. Any idea why? cpantesters shows passes for Strawberry perl on 5.8.9 and 5.10.0 http://matrix.cpantesters.org/?dist=Devel-NYTProf%202.10;reports=1;os=MSWin32 Does make test pass for you? > > msvcrt.dll!77c47094() > [Frames below may be incorrect and/or missing, no symbols loaded for > msvcrt.dll] > perl510.dll!6a731b89() > perl510.dll!6a69c77f() > perl510.dll!6a72fdaf() > perl510.dll!6a731a51() > perl510.dll!6a730579() > perl510.dll!6a731d90() > perl510.dll!6a731d90() > [...] Ug. Can't do much with that! Any way you could get a more detailed stact trace? Perhaps by rebuilding perl with -g and -DDEBUGGING enabled in the config. And/or try "perl Makefile.PL -g", though that might only help show detail for NYTProf subs and the stack trace seems to indicate the crash is deep inside perl. 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] -~----------~----~----~----~------~----~------~--~---
