On Wed, Feb 24, 2010 at 04:03:52PM +0000, Nicholas Clark wrote: > On Wed, Feb 24, 2010 at 03:46:08PM +0000, Tim Bunce wrote: > > On Wed, Feb 24, 2010 at 02:43:44PM +0000, Nicholas Clark wrote:
> > > I have no idea what to do next. > > > > Me neither. The 1.25 doesn't make much sense. I can't think that this bug is *helping*: http://www.freebsd.org/cgi/query-pr.cgi?pr=78787 sysconf(_SC_CLK_TCK) returns a contstant value defined in src/sys/i386/include/ansi.h this is not correct as the actual value of the statistics clock is not a constnat. In particular it is 100Hz on my system, but the constant returned is 128. The stat clock may be 100Hz is apm is enabled with flags 0x20 in the kernel file Usually I like FreeBSD a lot, but every second year there is a "WTF?" moment like this. [The previous one was about undocumented bogus non-failure return values in /proc for the FreeBSD equivalent of Linux's /proc/self/exe] However, even if I hard code things to 100 it doesn't pass. (or make sense) Nicholas Clark -- 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]
