Changes between Version 7 and Version 8 of Developer/Projects/Open/TraceTool

Timestamp:

08/07/09 20:28:17 (15 years ago)

Author:

Cocanlucian

Comment:

Developer/Projects/Open/TraceTool

@@ -14 +14 @@
 This section specifies paths to other configuration files (called API configuration files) which contain information that is needed for the encoding of data and generation of ID's (functions ID, manager ID, API id etc). The section  “API configuration files” explains what these configuration files should contain. Check this for an example.
 
-#rtems-functions: list of comma separated function names
+   1. rtems-functions: list of comma separated function names
 This section should contain a list of comma separated function names that the user wants to trace. Check this for an example.
 
-#rtems-managers: list of comma separated manager names
+   2. rtems-managers: list of comma separated manager names
 This section should contain a list of comma separated manager names. The manager names should be specified like this: API_name-manager_name. This is to help the user to specify more easily hole sets of functions. 
 Ex: If the user wants to trace all the functions from the task manager from the Classic API then he could do this:
 
-rtems-manager: classic-task
+   3. rtems-manager: classic-task
 
 Rather than doing this:
 
-rtems-functions: rtems_task_create, rtems_task_ident 
+   4. rtems-functions: rtems_task_create, rtems_task_ident 
                  rtems_task_self, rtems_task_start 
                  rtems_task_restart, rtems_task_delete
@@ -38 +38 @@
         I think you got the point. :)
 
-rtems-libraries: list of comma separated library names
+   5. rtems-libraries: list of comma separated library names
         This section should contain a list of comma separated library names. Check this for an example.
 
-rtems-symbols-path: path to the folder containing the symbols files
+   6. rtems-symbols-path: path to the folder containing the symbols files
 
         This section should contain a valid path to a directory containing the symbols files. The symbols files (functions.sym, structs.sym, typedefs.sym, unions.sym) contain information, as their name suggest, about functions signature, struct, typedef and union definition. These files are specific to a library and should be found in a directory that has the same name as the library from which the files resulted.
@@ -51 +51 @@
 # Sample configuration file
 # Include section
-include "rtems_trace_classic.cfg"
-include "rtems_trace_posix.cfg"
+'''include''' "rtems_trace_classic.cfg"
+'''include''' "rtems_trace_posix.cfg"
 
 # The user can specify just some functions specific to an API to trace 
 # or a hole set of functions specific to a manager from an API.
 # Specify some functions.
-rtems-functions: rtems_task_create, rtems_task_delete
+'''rtems-functions''': rtems_task_create, rtems_task_delete
 
 # Specify a manager from an API.
 # API_name-manager_name
-rtems-api: classic-task, classic-interrupt, classic-clock, classic-timer, classic-semaphore,
+'''rtems-api'''': classic-task, classic-interrupt, classic-clock, classic-timer, classic-semaphore,
            classic-message, classic-event, classic-signal, classic-io, classic-init,
            posix-mutex, posix-semaphore, posix-clock, posix-timer, posix-condvar,
@@ -68 +68 @@
 # Specify a path 
 # The path to the symbols files.
-rtems-symbols-path: /home/cocan/Faculta/RTEMS/gsoc_2009/branch-rtems-trace/rtems-trace/bin/rtems-trace/symbols/librtems/
+'''rtems-symbols-path''': /home/cocan/Faculta/RTEMS/gsoc_2009/branch-rtems-trace/rtems-trace/bin/rtems-trace/symbols/librtems/
 
 = API configuration file =