Re: Profiling Ada applications using gprof

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2018-12-05 17:05, joakimds@kth.se wrote:
> When Writing code oneself one could use select-statements to discover long running entry calls like:
> 
>     procedure Work is
>     begin
>        select
>           delay 1.0;
>           Ada.Text_IO.Put_Line ("Calling A.Stop takes too long time!");
>        then abort
>           A.Stop;
>        end select;
>     end Work;
> 
> But again, it would be cool if there was a way to discover long running entry calls by profiling (for example gprof).

This is not an entry call, it is asynchronous transfer of control (RM 
9.7.4).

Regarding entry calls, a long running call of a protected entry is a 
bug, protected actions must be instant, nothing to profile. For a task 
entry, it is maybe not a quite bug, but suspicious nonetheless. Though, 
I presume that both must be detectable by the profiler.

I guess you mean something completely different - times spent by a task 
in a queue of an entry, multiple entries if requeue happens. That would 
be a quite cool feature indeed.

The total time of an entry call as observed by the caller is

    time spent in the queues + execution time of the entry body

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de