@@ Line 80: / Line 80: @@
 {{hidden begin
-|title = 1. What lanuages can gprof profile?
+|title = 1. What is a call graph?
 }}
 <quiz display=simple>
 {
 |type="()"}
--  Python, Java, Julia
+-
-||
+|| An android app to show incoming callers
-+  C/C++, Fortran, Pascal
++
-|| True
+|| A hierarchy diagram of function calls in a given profile
--  Haskell, Cobol, Brainfuck
+-
-||
+|| Instructions of how to call for help during emergencies
+</quiz>
+{{hidden end}}
+{{hidden begin
+|title = 2. How do you generate a callgraph of a gprof profile?
+}}
+<quiz display=simple>
+{
+|type="()"}
+-
+|| gprof --call-graph
+-
+|| gprof
++
+|| gprof --graph
+</quiz>
+{{hidden end}}
+{{hidden begin
+|title = 3. What is gprof2dot?
+<quiz display=simple>
+{
+|type="()"}
++
+|| Third party script for call graph visualization via the "dot" library
+-
+|| Gprof feature to export profiles as a pdf
+-
+|| A fork of the beta version of gprof2
+</quiz>
+{{hidden end}}
+{{hidden begin
+|title = 4. Does gprof work with MPI applications?
+<quiz display=simple>
+{
+|type="()"}
+-
+|| No, gprof only works with sequential applications
+-
+|| Yes, parallel profiling is the main use case of gprof
++
+|| Yes, but gprof cannot differentiate between individual threads/processes
+</quiz>
+{{hidden end}}
+{{hidden begin
+|title = 5. How much overhead does gprof produce?
+<quiz display=simple>
+{
+|type="()"}
+-
+|| None
++
+|| Little
+-
+|| Much
 </quiz>
 {{hidden end}}

	By instrumenting the application during compilation.
	Through static analysis of the source code

	Simple and understandable
	Representative of the usual workload
	Covering edge cases

Difference between revisions of "Gprof Tutorial"

Revision as of 12:56, 2 November 2020