touch-packages team mailing list archive

[Matthias Klose <doko@xxxxxxxxxx>]

please report this issue upstream; won't fix this in Ubuntu only.

** Changed in: binutils (Ubuntu)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/398431

Title:
  gprof reports time in nanoseonds, but explanatory text refers to
  milliseconds

Status in “binutils” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: binutils

  Program: GNU gprof (GNU Binutils for Ubuntu) 2.19.1

  binutils:
    Installed: 2.19.1-0ubuntu3
    Candidate: 2.19.1-0ubuntu3
    Version table:
   *** 2.19.1-0ubuntu3 0
          500 http://us.archive.ubuntu.com jaunty/main Packages
          100 /var/lib/dpkg/status

  OS: Linux eeepc 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51
  UTC 2009 i686 GNU/Linux (Jaunty)

  
  When I profile my program, I get a value of time per call that is in nanoseconds.  However, the explanatory text concerning time/call discusses milliseconds.  Please see below for an example.

  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
  * * * * * * * * * * * * * * * * * * * *

  Each sample counts as 0.01 seconds.
    %   cumulative   self              self     total           
   time   seconds   seconds    calls  ns/call  ns/call  name    
   70.83      0.17     0.17                                            main
   29.17      0.24     0.07   990001    70.71    70.71   inv

  Note that this says 70.71 ns/call.

  However, the text that explains the time per call reads as follows:

   self         the average number of milliseconds spent in this
  ms/call    function per call, if this function is profiled,
                  else blank.

   total       the average number of milliseconds spent in this
  ms/call    function and its descendents per call, if this 
                  function is profiled, else blank.

  Note that here we're talking about milliseconds.

  The numbers are off by a factor of a million, which is probably too
  much.  I understand that with profiling you're looking more for
  *relative* times, not absolutes.  However, whatever times we're
  considering, there should be some sort of agreement between the basic
  units.

  This is not a critical bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/398431/+subscriptions