Changes between Version 27 and Version 28 of Developer/Projects/Open/TraceTool


Ignore:
Timestamp:
Aug 10, 2009, 1:09:08 PM (10 years ago)
Author:
Cocanlucian
Comment:

Legend:

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

    v27 v28  
    3636Example: If the user wants to trace all the functions from the task manager from the Classic API then he could do this:
    3737
    38    rtems-manager: classic-task
     38   rtems-managers: classic-task
    3939
    4040Rather than doing this:
     
    6464   # Include section
    6565   '''include''' "rtems_trace_classic.cfg"
    66    '''include''' "rtems_trace_posix.cfg"
     66   '''include''' "rtems_trace_posix.cfg" <BR>
    6767   # The user can specify just some functions specific to an API to trace
    6868   # or a hole set of functions specific to a manager from an API.
    6969   # Specify some functions.
    70    '''rtems-functions''': rtems_task_create, rtems_task_delete
     70   '''rtems-functions''': rtems_task_create, rtems_task_delete <BR>
    7171   # Specify a manager from an API.
    72    # API_name-manager_name
    73    '''rtems-api'''': classic-task, classic-interrupt, classic-clock, classic-timer, classic-semaphore,
     72   # API_name-manager_name <BR>
     73   '''rtems-managers'''': classic-task, classic-interrupt, classic-clock, classic-timer, classic-semaphore,
    7474               classic-message, classic-event, classic-signal, classic-io, classic-init,
    7575               posix-mutex, posix-semaphore, posix-clock, posix-timer, posix-condvar,
    7676               posix-scheduler, posix-message
    77    # Specify a path
     77   # Specify a path  <BR>
    7878   # The path to the symbols files.
    7979   '''rtems-symbols-path''': /home/cocan/Faculta/RTEMS/gsoc_2009/branch-rtems-trace/rtems-trace/bin/rtems-trace/symbols/librtems/