Difference between revisions of "Info Predefined Probe"

From OC Systems Wiki!
Jump to: navigation, search
(Created page with "== Info Probe: info.ual == The '''info.ual''' predefined probe provides the user with the general information available about the program. It can be used on an executable bef...")
 
m (Info Probe: info.ual)
 
Line 5: Line 5:
 
The most common use of this probe is to get the names of the target program's entry points for which one can define a probe. Without using this probe, it is sometimes difficult to come up with the exact name of the function, that would be understood by Aprobe. Using this probe ensures that the one refers to target functions by the same name as does Aprobe.
 
The most common use of this probe is to get the names of the target program's entry points for which one can define a probe. Without using this probe, it is sometimes difficult to come up with the exact name of the function, that would be understood by Aprobe. Using this probe ensures that the one refers to target functions by the same name as does Aprobe.
  
Using '''info.ual '''directly with aprobe is made unnecessary by the '''apinfo''' and '''apsymbols''' commands (see [aprobe-9.html#MARKER-9-1052 "apinfo"] and [aprobe-9.html#MARKER-9-1110 "apsymbols"]). These are scripts which pass invoke aprobe using <code>info.ual</code> and simplify the handling of the parameters and other files.
+
Using '''info.ual '''directly with aprobe is made unnecessary by the '''apinfo''' and '''apsymbols''' commands (see [[AUG_Tools_Reference#apinfo|apinfo]] and [[AUG_Tools_Reference#apsymbols|apsymbols]]). These are scripts which pass invoke aprobe using <code>info.ual</code> and simplify the handling of the parameters and other files.
  
Another important use of this probe is at format time to get the names of all the [aprobe-10.html#MARKER-9-1336 UAL file]s that were used to collect the data at runtime. This is especially useful in lab environments where the multiple users may be collecting different data using different UALs on the same executable at the same time.
+
Another important use of this probe is at format time to get the names of all the [[AUG_Files_Reference#UAL|UAL file]]s that were used to collect the data at runtime. This is especially useful in lab environments where the multiple users may be collecting different data using different UALs on the same executable at the same time.
  
 
=== Usage ===
 
=== Usage ===
  
'''info.ual''' is specified on the [aprobe-9.html#MARKER-9-1075 aprobe] or [aprobe-9.html#MARKER-9-1035 apformat] command line. The specific options are:
+
'''info.ual''' is specified on the [[AUG_Tools_Reference#aprobe|aprobe]] or [[AUG_Tools_Reference#apformat|apformat]] command line. The specific options are:
<code>
+
 
 
  aprobe -u '''info.ual''' [-p " param_list '''"] executable apformat''' -u '''info.ual''' [-p  '''" param_list " '''] apd_file
 
  aprobe -u '''info.ual''' [-p " param_list '''"] executable apformat''' -u '''info.ual''' [-p  '''" param_list " '''] apd_file
</code>
+
 
 
where ''param_list'' may include:
 
where ''param_list'' may include:
  
Line 45: Line 45:
  
 
For example, the command
 
For example, the command
  <code>
+
 
  aprobe -u info<code>.ual</code> -p "-s" a.out
+
  aprobe -u info<code>.ual</code> -p "-s" a.out
</code
+
 
 
Provides the same output as the command "<code>apsymbols a.out</code>".
 
Provides the same output as the command "<code>apsymbols a.out</code>".
  
 
If one doesn't know what UALs were used in data collection at runtime, he can get this information with the following command:
 
If one doesn't know what UALs were used in data collection at runtime, he can get this information with the following command:
  <code>
+
 
  apformat -u info<code>.ual</code> -p "-u" a.apd
+
  apformat -u info<code>.ual</code> -p "-u" a.apd
</code>
+
 
  
  

Latest revision as of 06:32, 20 March 2018

Info Probe: info.ual

The info.ual predefined probe provides the user with the general information available about the program. It can be used on an executable before the program is run, or with apformat to see additional information about the program after it was run.

The most common use of this probe is to get the names of the target program's entry points for which one can define a probe. Without using this probe, it is sometimes difficult to come up with the exact name of the function, that would be understood by Aprobe. Using this probe ensures that the one refers to target functions by the same name as does Aprobe.

Using info.ual directly with aprobe is made unnecessary by the apinfo and apsymbols commands (see apinfo and apsymbols). These are scripts which pass invoke aprobe using info.ual and simplify the handling of the parameters and other files.

Another important use of this probe is at format time to get the names of all the UAL files that were used to collect the data at runtime. This is especially useful in lab environments where the multiple users may be collecting different data using different UALs on the same executable at the same time.

Usage

info.ual is specified on the aprobe or apformat command line. The specific options are:

aprobe -u info.ual [-p " param_list "] executable apformat -u info.ual [-p  " param_list " ] apd_file

where param_list may include:

-a
Prints all information.
-d
Print data symbols from application module.
-da
Print data symbols from all modules.
-h
Prints options.
-l
Prints instrumentable lines for each function symbol shown.
-m
Prints the list of modules and their checksums.
-s
Prints function names from the application module.
-sa
Prints function names from all modules.
-t
Prints the list of threads (format-time only)
-u
Prints the list of UALs used at runtime (format-time only)
'-x'
Indicate functions that are not instrumentable.
'-xb'
Exclude listing functions that are not instrumentable.
'-xg'
Exclude listing functions that are instrumentable.

For example, the command

aprobe -u info.ual -p "-s" a.out

Provides the same output as the command "apsymbols a.out".

If one doesn't know what UALs were used in data collection at runtime, he can get this information with the following command:

apformat -u info.ual -p "-u" a.apd