On Fri, Jun 12, 2009 at 04:07:42PM +0100, Martin Evans wrote: > Just realised I may have sent this originally to an address you don't > use. If you've seen it already - sorry.
Not so much "don't use" as "don't read". My [email protected] copies my emails to [email protected] so I can use gmail as my "searchable remote email archive", but I don't read emails that are sent directly there. > Hi Tim, > > I'm getting a lot of these. I am unsure whether to rt this so decided to > run it by you first. I found a reference in the HACKING file saying: > > Investigate and fix "Unable to determine line number" cases. Here's one: > > $ NYTPROF=begin=1:blocks=1:trace=1 perl -d:NYTProf -Mstrict -e 1 > > and tried setting NYTPROF as above and I get: > > NYTPROF=begin=1:blocks=1:trace=1 perl -d:NYTProf -MCarp=verbose -I > /home/martin/bet/tools/modules/BET/lib/ -t refreshd.pl > Unknown NYTProf option: 'begin' <--------- notice I'll update the HACKING file, it's a bit dated. Thanks. > # trace=1 > NYTProf init pid 5037, clock 1 > Opened nytprof.out > NYTProf enable_profile (previously disabled) to nytprof.out at > /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/Devel/NYTProf.pm > line 43. > Unable to determine line number in refreshd.pl. > NYTProf pid 5037: first statement line 0 of refreshd.pl. > Unable to determine line number in refreshd.pl. > Unable to determine line number in refreshd.pl. > Unable to determine line number in refreshd.pl. > Unable to determine line number in refreshd.pl. > > Is there something I can do to track these down? It probably requires wading deep into the guts of perl. If this means anything to you then you've got a hope: /* Might be a cop that has been optimised away. We can try to find such a * cop by searching through the optree starting from the sibling of PL_curcop. I've been working on the basis that I'll ignore it till someone complains. I guess you just have! Start digging and see where it takes you. If you run into questions I'll give (fairly uneducated) pointers and, if we're lucky, Nick may give us some educated pointers. Tim. p.s. It's worth noting that I implemented parts of the guts of NYTProf using the "keep kicking it till it does the right thing" approach. See the comment above the PL_curcop_nytprof definition for one example. It would be a big help is someone with more guts, especially compiler guts, experience would look over the code. --~--~---------~--~----~------------~-------~--~----~ 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] -~----------~----~----~----~------~----~------~--~---
