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


Ignore:
Timestamp:
Aug 7, 2009, 8:29:37 PM (10 years ago)
Author:
Cocanlucian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Open/TraceTool

    v8 v9  
    1111        In order for the rtems-trace tool to function correctly the user must provide a configuration file which should have the following format and include the following sections:
    1212
    13 #include "path_to_an_API_config_file"
     13   1. include "path_to_an_API_config_file"
    1414This 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.
    1515
    16    1. rtems-functions: list of comma separated function names
     16   2. rtems-functions: list of comma separated function names
    1717This section should contain a list of comma separated function names that the user wants to trace. Check this for an example.
    1818
    19    2. rtems-managers: list of comma separated manager names
     19   3. rtems-managers: list of comma separated manager names
    2020This 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.
    2121Ex: If the user wants to trace all the functions from the task manager from the Classic API then he could do this:
    2222
    23    3. rtems-manager: classic-task
     23   4. rtems-manager: classic-task
    2424
    2525Rather than doing this:
    2626
    27    4. rtems-functions: rtems_task_create, rtems_task_ident
     27   5. rtems-functions: rtems_task_create, rtems_task_ident
    2828                 rtems_task_self, rtems_task_start
    2929                 rtems_task_restart, rtems_task_delete
     
    3636                 rtems_task_variable_delete
    3737
    38         I think you got the point. :)
    39 
    40    5. rtems-libraries: list of comma separated library names
     38   6. rtems-libraries: list of comma separated library names
    4139        This section should contain a list of comma separated library names. Check this for an example.
    4240
    43    6. rtems-symbols-path: path to the folder containing the symbols files
    44 
    45         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.
     41   7. rtems-symbols-path: path to the folder containing the symbols files
     42This 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.
    4643
    4744        Below is a sample configuration file.
     
    5148# Sample configuration file
    5249# Include section
    53 '''include''' "rtems_trace_classic.cfg"
     50'''include''' "rtems_trace_classic.cfg" 
    5451'''include''' "rtems_trace_posix.cfg"
    5552