On Fri, Jul 03, 2009 at 11:50:23AM -0500, Elliot Shank wrote: > > Tim Bunce wrote: > > That last line smells of an integer overflow to me. The large negative > > overhead would have added 214s to A (incl_subr_sec). That seems to fit > > what happend on line 6 of the trace, but I'm not sure if it sheds any > > light on line 5 and I'm way over time on this. > > During compilation, there is a warning about a cast between an integer and a > pointer of different sizes.
Giving me a copy of the message, with details of the line number etc., would be kind'a helpful :) > > I've no idea why that int cast was in there. It would be most likely to > > affect a user with a 32-bit perl, on a system with posix realtime clock > > (and thus a 10ns tick interval) profiling a long running process. > > > > I'm guessing that's a good description of you :-) > > This is on a 64 bit box, but I don't remember whether the perl is that > partially 64 bit setup or not. I'll include the -V output next time. It's just a question of if the 'int' type is 32 or 64 bit. > > I've checked in a bunch of changes, including this one and some others > > that may also be bug fixes. > > > > So, can you give r796 a whirl and let us know how it goes? > > I'll do so on Monday (U.S. holiday weekend). Great. Thanks. 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] -~----------~----~----~----~------~----~------~--~---
