DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Analyzing run-time behavior

Relinking the program

You do not need to recompile code to do block profiling. However, the executables and shared objects that use the code does need to be relinked.

Using the same example described previously:

If the code is usually compiled this way:

   $ cc -c travel.c
   $ cc -c misc.c
   $ cc -o travel travel.o misc.o

Change it to:

   $ cc -c travel.c
   $ cc -c misc.c
   $ ld -r -o all.o travel.o misc.o
   $ fur -b all -c mklog all.o
   $ cc -o travel all.o log.all.o
Notice that the code is compiled the same way, so if you have retained the .o files you don't have to recompile the code. mklog automatically produces log.all.o for you.
Next topic: Running the experiment
Previous topic: Using fur to perform block profiling

© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 02 June 2005