On Wednesday, 29 June 2011 10:41:58 UTC+1, Tim.Bunce wrote: > > On Tue, Jun 28, 2011 at 12:46:51AM -0700, Martin wrote: > > Hi, > > > > I run Devel::NYTProf all the time and have no problems with it until > > this morning. Now I get quite a lot of the above warning (around 8). 1 > > is my own module and the others are things like: > > > > fid 23 has no src saved for /home/martin/perl5/perlbrew/perls/ > > perl-5.14.0/lib/5.14.0/Getopt/Std.pm (NYTP_FIDf_HAS_SRC not set but > > src available!) > > fid 193 has no src saved for /home/martin/perl5/perlbrew/perls/ > > perl-5.14.0/lib/5.14.0/Benchmark.pm (NYTP_FIDf_HAS_SRC not set but src > > available!) > > It's certainly odd. > > > I cannot see what is common between them and I'm at a loss to think > > what I may have done to cause this. > > Yes, the obvious question is "what changed?" > That could be a difficult one to pinpoint as a lot is changing right now here. I will however try.
> > Even though the message is issued > > for B.pm the source is visible in the nytprofhtml output. > > nytprofhtml will fallback to reading the source directly from the file > path if it's not embedded into the profile. > ah, ok, I wondered why it was warning but appearing to work. > > perl is 5.14.0 installed via perlbrew. I do have PERL_UNICODE=SAL but > > I've had that some time and unsetting it made no difference. I > > couldn't find anyone else with this issue on google. > > I've not seen it before. The implication is that source code wasn't > available when the file was first 'noticed' by the profiler (so > NYTP_FIDf_HAS_SRC didn't get set), but was available when the profile > as written out at the end of the run. > I cannot see how the source code would not be available at profile time but it is later. Also, all modules mentioned are in my home directory - either under the Perl installed via perlbrew or our own modules in my account. > Looking at svn blame etc I see that that check was included in the > initial implementation of saving the source code. > > If you can't retrace your steps to find the cause, which I hope you can, > then you could send me a trace file. Level 4 should suffice. > (I can't promise I'll even look at it though as I'm rather snowed under > with a different kind of project: http://yfrog.com/z/h0paexycj ) > I see you look very busy so I'll poke around a bit more myself. Just thought someone might have seen the issue before. Thanks > Tim. > BTW, watch what you are doing with those kuboto diggers. We hired one for a a few weeks years ago and my wife managed to get it stuck between 2 brick wall posts when it sank unexpectedly. I had visions of having to hire a crane or knock the newly laid walls down. It took hours of gentle maneuvering to get it out. -- 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]
