From: joakimds@kth.se
Subject: Re: Profiling Ada applications using gprof
Date: Wed, 5 Dec 2018 07:32:52 -0800 (PST)
Date: 2018-12-05T07:32:52-08:00 [thread overview]
Message-ID: <b2a3692e-a53d-4be2-96d2-510400b08ffd@googlegroups.com> (raw)
In-Reply-To: <5846093f-ace9-4c8b-b4d7-d714b787d477@googlegroups.com>
> Isn't a or missing before delay 10.0? The rendoz-vous will always take 10 sec. > And then you can skip the do thing:
That's correct but consider the following thought experiment: Imagine being new in an Ada project with a mature code base which has been worked on for 20+ years and is around 2 million lines of Ada code. Imagine it takes a long time to shut down the application and the question is how to quickly find out why. Maybe somebody has put a long running calculation by mistake inside an entry call like in the example above where a delay statement has been used instead to simulate work being done. How is there any hope to find out quickly in the huge code base if it isn't possible in the tiny example code I have provided in the original post? How can one avoid manual inspection/review?
next prev parent reply other threads:[~2018-12-05 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 15:04 Profiling Ada applications using gprof joakimds
2018-12-04 19:41 ` Dennis Lee Bieber
2018-12-05 14:13 ` Petter Fryklund
2018-12-05 15:32 ` joakimds [this message]
2018-12-05 16:05 ` joakimds
2018-12-05 17:27 ` Dmitry A. Kazakov
2018-12-05 20:11 ` Dennis Lee Bieber
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox