Changes between Version 1 and Version 2 of Tracing


Ignore:
Timestamp:
2009-05-01T12:47:57Z (16 years ago)
Author:
Jiri Svoboda
Comment:

Make use of L1 headings.

Legend:

Unmodified
Added
Removed
Modified
  • Tracing

    v1 v2  
    1 == Using the Syscall/IPC Tracer ==
     1= Using the Syscall/IPC Tracer =
    22
    33The tracer application (/app/trace) is meant to give you a rough idea about what your application is doing by printing the system calls it is making. However, since HelenOS is a microkernel system, the system calls are not all that interesting, since they are mostly just IPC calls. For this reason, the tracer tries to analyze communication on higher layers to a certain extent, i.e. the IPC communication and (in a very primitive way) the application protocols.
    44
    5 === Command-line parameters ===
     5== Command-line parameters ==
    66
    77To execute a program and trace it, type
     
    2828}}}
    2929
    30 === Keyboard controls ===
     30== Keyboard controls ==
    3131
    3232Press 'Q' anytime to quit the tracing application.
    3333
    34 === Understanding the output ===
     34== Understanding the output ==
    3535
    3636A typical application-protocol message has the form:
     
    4646Here ''phone_id'' is the ID of the phone on which the request is being made. The ''protocol'' field is the name of the protocol that the tracer believes is being used on that phone. (This is normally detected by spying on the communication with the naming service.) The ''method'' is a textual representation of the IPC method number (for that protocol). The period (`.`) at the end of the line denotes that the request returns no value (and thus the response will not be displayed).
    4747
    48 === Notes ===
     48== Notes ==
    4949
    5050 * Decoding tables for application protocols are currently very incomplete. Unrecognized calls are not printed at all at the ''protocol'' level, you must display IPC-level messages (`+i`) to see them!