Simple question about profiling

2003-02-20 Thread Paolo Pisati

I've to confess this my first serious profile session, and
i found something really strange (at least for me... =P)

[flag@law3 src]$ gprof proto3
[snip]
 %   cumulative   self  self total
 time   seconds   secondscalls  ms/call  ms/call  name
 74.4  39.2639.26 .mcount (83)
  6.7  42.82 3.56 111575600 0.00 0.00  checkRule2d [4]
  6.6  46.30 3.48 1024 3.3912.30  buildTree2d [3]
  3.8  48.29 1.99 117334464 0.00 0.00  add_tail [6]
  3.7  50.25 1.96 117234464 0.00 0.00  rem [7]
  1.8  51.18 0.93 117234464 0.00 0.00  rem_head [5]
  0.6  51.51 0.33  164 0.00 0.00  __qdivrem [13]
  0.5  51.75 0.24   84 0.00 0.00  __svfscanf [9]
  0.4  51.96 0.21 9037 0.02 0.09  buildTree1d [10]
  0.3  52.14 0.18   80 0.00 0.00  strtoumax [12]
  0.3  52.28 0.14  1078414 0.00 0.00  memset [20]
  0.2  52.41 0.12  5658864 0.00 0.00  checkRule1d [21]
  0.1  52.47 0.07   250129 0.00 0.00  count [23]
  0.1  52.52 0.05   537809 0.00 0.00  malloc_bytes  [22
]
  0.1  52.56 0.04  1166299 0.00 0.00  append_lists [25]
  0.1  52.59 0.03  2411019 0.00 0.00  new_list [26]
  0.1  52.62 0.03   536551 0.00 0.00  calloc [14]
  0.0  52.64 0.02   70 0.24 0.42  tree2dHeight [29]
[snip]

i think this is the beef: what the hell is .mcount?!?!
if i read the table correctly, .mcount is the guilty, isn't it?

any help or pointer is appreciated, thank you... =)

-- 

Paolo

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Simple question about profiling

2003-02-18 Thread Paolo Pisati

I've to confess this my first serious profile session, and
i found something really strange (at least for me... =P)

[flag@law3 src]$ gprof proto3
[snip]
 %   cumulative   self  self total
 time   seconds   secondscalls  ms/call  ms/call  name
 74.4  39.2639.26 .mcount (83)
  6.7  42.82 3.56 111575600 0.00 0.00  checkRule2d [4]
  6.6  46.30 3.48 1024 3.3912.30  buildTree2d [3]
  3.8  48.29 1.99 117334464 0.00 0.00  add_tail [6]
  3.7  50.25 1.96 117234464 0.00 0.00  rem [7]
  1.8  51.18 0.93 117234464 0.00 0.00  rem_head [5]
  0.6  51.51 0.33  164 0.00 0.00  __qdivrem [13]
  0.5  51.75 0.24   84 0.00 0.00  __svfscanf [9]
  0.4  51.96 0.21 9037 0.02 0.09  buildTree1d [10]
  0.3  52.14 0.18   80 0.00 0.00  strtoumax [12]
  0.3  52.28 0.14  1078414 0.00 0.00  memset [20]
  0.2  52.41 0.12  5658864 0.00 0.00  checkRule1d [21]
  0.1  52.47 0.07   250129 0.00 0.00  count [23]
  0.1  52.52 0.05   537809 0.00 0.00  malloc_bytes  [22
]
  0.1  52.56 0.04  1166299 0.00 0.00  append_lists [25]
  0.1  52.59 0.03  2411019 0.00 0.00  new_list [26]
  0.1  52.62 0.03   536551 0.00 0.00  calloc [14]
  0.0  52.64 0.02   70 0.24 0.42  tree2dHeight [29]
[snip]

i think this is the beef: what the hell is .mcount?!?!
if i read the table correctly, .mcount is the guilty, isn't it?

any help or pointer is appreciated, thank you... =)

-- 

Paolo

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message