Pssible Bug in Python Profiler

Discussion in 'Python' started by Christoph Becker-Freyseng, Aug 13, 2003.

  1. Hello,

    I started some profiling with '2.1.3 (#1, Sep 7 2002, 15:29:56) \n[GCC
    2.95.4 20011002 (Debian prerelease)]' and got the following output:

    6067913 function calls in -3311.947 CPU seconds

    Also the cumulative times are affected (at least of some calls)

    It took some time to run my program and so I guess there's a overflow in
    the seconds counter.
    Ideas? Suggestions?


    Thank You,
    Christoph Becker-Freyseng
     
    Christoph Becker-Freyseng, Aug 13, 2003
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. puzzlecracker

    pssible confusion about iterators

    puzzlecracker, Sep 28, 2005, in forum: C++
    Replies:
    0
    Views:
    277
    puzzlecracker
    Sep 28, 2005
  2. puzzlecracker

    pssible confusion about iterators

    puzzlecracker, Sep 28, 2005, in forum: C++
    Replies:
    5
    Views:
    280
    red floyd
    Sep 29, 2005
  3. potatosoftware
    Replies:
    0
    Views:
    663
    potatosoftware
    Nov 4, 2009
  4. DaZoner

    Profiler bug in 1.8.2?

    DaZoner, Jan 7, 2005, in forum: Ruby
    Replies:
    4
    Views:
    112
    Matt Mower
    Jan 9, 2005
  5. it_says_BALLS_on_your forehead

    Bug in Perl Profiler?

    it_says_BALLS_on_your forehead, Jul 27, 2006, in forum: Perl Misc
    Replies:
    6
    Views:
    103
    it_says_BALLS_on_your forehead
    Jul 28, 2006
Loading...

Share This Page