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


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

Legend:

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

    v7 v8  
    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 #rtems-functions: list of comma separated function names
     16   1. 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 #rtems-managers: list of comma separated manager names
     19   2. 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 rtems-manager: classic-task
     23   3. rtems-manager: classic-task
    2424
    2525Rather than doing this:
    2626
    27 rtems-functions: rtems_task_create, rtems_task_ident
     27   4. rtems-functions: rtems_task_create, rtems_task_ident
    2828                 rtems_task_self, rtems_task_start
    2929                 rtems_task_restart, rtems_task_delete
     
    3838        I think you got the point. :)
    3939
    40 rtems-libraries: list of comma separated library names
     40   5. rtems-libraries: list of comma separated library names
    4141        This section should contain a list of comma separated library names. Check this for an example.
    4242
    43 rtems-symbols-path: path to the folder containing the symbols files
     43   6. rtems-symbols-path: path to the folder containing the symbols files
    4444
    4545        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.
     
    5151# Sample configuration file
    5252# Include section
    53 include "rtems_trace_classic.cfg"
    54 include "rtems_trace_posix.cfg"
     53'''include''' "rtems_trace_classic.cfg"
     54'''include''' "rtems_trace_posix.cfg"
    5555
    5656# The user can specify just some functions specific to an API to trace
    5757# or a hole set of functions specific to a manager from an API.
    5858# Specify some functions.
    59 rtems-functions: rtems_task_create, rtems_task_delete
     59'''rtems-functions''': rtems_task_create, rtems_task_delete
    6060
    6161# Specify a manager from an API.
    6262# API_name-manager_name
    63 rtems-api: classic-task, classic-interrupt, classic-clock, classic-timer, classic-semaphore,
     63'''rtems-api'''': classic-task, classic-interrupt, classic-clock, classic-timer, classic-semaphore,
    6464           classic-message, classic-event, classic-signal, classic-io, classic-init,
    6565           posix-mutex, posix-semaphore, posix-clock, posix-timer, posix-condvar,
     
    6868# Specify a path
    6969# The path to the symbols files.
    70 rtems-symbols-path: /home/cocan/Faculta/RTEMS/gsoc_2009/branch-rtems-trace/rtems-trace/bin/rtems-trace/symbols/librtems/
     70'''rtems-symbols-path''': /home/cocan/Faculta/RTEMS/gsoc_2009/branch-rtems-trace/rtems-trace/bin/rtems-trace/symbols/librtems/
    7171
    7272= API configuration file =