[erlang-bugs] eprof overflow causes incorrect analysis

Björn-Egil Dahlberg egil@REDACTED
Thu Nov 24 14:26:30 CET 2011


On 2011-11-24 13:08, Jonas Boberg wrote:
> Hi,
>
> Looks like there is an integer overflow or similar in eprof:
>
> 37>  eprof:analyze(total).
> FUNCTION                                                      CALLS
>     %           TIME       [  uS / CALLS]
> ets:lookup/2                                                    15948
>    0.00          21003  [       1.32]
> erlang:setelement/3                                          90211
> 0.00          24342  [       0.27]
> erlang:port_control/3                                         19667
> 0.00         101628  [       5.17]
> prim_inet:enum_val/2                                        21664
> 100.00  1000000008142  [46159527.70]
>
> The last row is obviously incorrect (profiling was active for about 5
> second).  This is when profiling a moderately loaded node.
> I can consistently reproduce the problem. If I reduce the time of
> profiling (so that less function calls are made) I don't get this
> problem.
Can you send me a test module so I can reproduce this?

// Björn-Egil



More information about the erlang-bugs mailing list