From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a6b:7512:: with SMTP id l18mr4758156ioh.31.1544025930534; Wed, 05 Dec 2018 08:05:30 -0800 (PST) X-Received: by 2002:a9d:24c3:: with SMTP id z61mr455649ota.1.1544025930408; Wed, 05 Dec 2018 08:05:30 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.166.215.MISMATCH!k10no104120itk.0!news-out.google.com!v141ni113ita.0!nntp.google.com!q69no103790itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 5 Dec 2018 08:05:30 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=136.163.203.3; posting-account=HFCrOQoAAABZD_f-UUbYHm3lJDIrh-UX NNTP-Posting-Host: 136.163.203.3 References: <8441254e-f634-4077-b8d9-d988dab3406c@googlegroups.com> <5846093f-ace9-4c8b-b4d7-d714b787d477@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <27bf087a-d64d-4e9f-89b8-e7a7df70f917@googlegroups.com> Subject: Re: Profiling Ada applications using gprof From: joakimds@kth.se Injection-Date: Wed, 05 Dec 2018 16:05:30 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader01.eternal-september.org comp.lang.ada:54960 Date: 2018-12-05T08:05:30-08:00 List-Id: 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).