CC: | Tim.Bunce [...] pobox.com, bug-devel-nytprof [...] rt.cpan.org, develnytprof-dev [...] googlegroups.com |
Subject: | Re: Weird errors using NYTProf |
Date: | Tue, 16 Sep 2008 16:11:05 +0100 |
To: | Thomas Equeter <thomas.equeter [...] ovh.net> |
From: | Tim Bunce <Tim.Bunce [...] pobox.com> |
On Tue, Sep 16, 2008 at 01:18:33PM +0200, Thomas Equeter wrote:
Show quoted text
> Hello,
>
> I'm trying to profile one of our Perl applications using NYTProf 2.03,
> and running into weird "can't happen" errors.
>
> But first, the setting: this is a relatively simple perl script (< 1K
> LoC) but it leverages a number of modules from our internal
> behemoth-sized library at OVH, so I can't really run it anywhere else
> than our dev and production servers.
>
> The details of our dev server are as follows: Linux 2.4.32 on i386, gcc
> 4.1.2, perl 5.8.8 (Debian-based). Needless to say that I can't alter any
> of that. However, I've also tried using a $HOME-installed perl 5.10.0,
> without any change in the symptoms.
Please post the perl -V output for both as it may be useful.
I've not been able to reproduce it with perl 5.8.6 or 5.10.0.
Show quoted text> Among the heap of weird errors that pop up whenever I add -d:NYTProf to
> the command-line, I've located an easily reproducible one at least:
>
> $ perl -MSocket6=AI_PASSIVE -e 'print AI_PASSIVE, "\n"'
> 1
> $ perl -MSocket6=AI_PASSIVE -d:NYTProf -e 'print AI_PASSIVE, "\n"'
> Unable to determine line number in -e.
> ...
> Your vendor has not defined Socket macro AI_PASSIVE, used at -e line 1
Please try running with NYTPROF=subs=0:blocks=0:leave=0:use_db_sub=1
and various combinations of value to isolate any that make a difference.
Also, could you hack a copy of Socket6? Modify the constant() function
(static double constant(char *name, int arg)) to print a copy of the
name argument, delimited by quotes, so we can see what it's getting.
Show quoted text> Also, the NYTProf test10 case fails (tests 46, 144, 242, 340):
>
> # got: 'test10.x line 3: got 0.0000000 expected ~2 for time'
> # expected: ''
Odd.
Can you try all the above with the current trunk code?:
http://code.google.com/p/perl-devel-nytprof/source/checkout
Show quoted text> Of course, none of this happens on my workstation, so I guess that it is
> somehow related to our dev server. Would you happen to have an idea of
> where the problem might lie and/or how to work around it?
Not yet.
Tim.