[xdebug-general] Re: AW: Re: Unusually long execution times

As far as I can see the most execution time of addslashes function is
4293967xxx µs, which is just a bit less then 2 ** 32. It seems that there
was an overflow in case the time period was calculated as negative.

I've seen similar cases (not with xdebug though) within virtual machine on
an amd opteron based server 2 years ago. We had our system clock jumping
back and forth continuously :)

On Wed, Aug 12, 2009 at 11:41 PM, André Hänsel <andre[@]webkr.de> wrote:

> > -----Ursprüngliche Nachricht-----
> > Von: xdebug-general-bounce[@]lists.xdebug.org [mailto:xdebug-general-
> > bounce[@]lists.xdebug.org] Im Auftrag von Derick Rethans
> > Gesendet: Mittwoch, 12. August 2009 16:19
> > An: André Hänsel
> > Cc: xdebug-general[@]lists.xdebug.org
> > Betreff: [xdebug-general] Re: Unusually long execution times
> >
> > WinCacheGrind is a factor of 10 off... it hasn't been adjusted for a
> > bug fix in Xdebug from 2.5 years ago :-/ I can't explain why
> > df_sqlval/is_bool are so slow though... there are 300000 calls to those
> > functions though. It is quite possible that Xdebug might be doing
> > something odd. Can you perhaps make a function trace?
>
> I included the source, the profiler output and a function trace in:
> http://kundenweb.creations.de/usenet/xdebug/xdebug.zip
>
> Regards,
> André
>
>
>
>
Received on Wed Aug 12 2009 - 19:17:36 BST