On Thu, Jul 16, 2009 at 07:32:26AM -0500, Elliot Shank wrote:
> 
> Tim Bunce wrote:
> > 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?
> 
> This was the simplest example in our codebase that I could immediately think 
> of and could reproduce the problem with.  There's no Moose involved.  :]

:)

> > 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?
> 
> Yes, the entire test suite works, both 2.10 and r812.  The only failure that 
> I was getting was test16 with r813-r828.

So the clock must be working. Odd. Perhaps the printf warnings have
fixed a problem that was causing 0's to be shown in the log.

> > 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.
> 
> I've been thinking of attempting to build my own copy of Strawberry,
> if only to change the path it gets installed to, so that I can have
> multiple versions around at a time.  But it doesn't exactly look
> simple; you've got to create a bootstrap build of perl first.

Perhaps you could persuade the Strawberry folk to make a debugging build
available.

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]
-~----------~----~----~----~------~----~------~--~---

Reply via email to