Changes between Version 1 and Version 2 of Tracing

Timestamp:

2009-05-01T12:47:57Z (15 years ago)

Author:

Jiri Svoboda

Comment:

Make use of L1 headings.

Tracing

@@ -1 @@
-== Using the Syscall/IPC Tracer ==
+= Using the Syscall/IPC Tracer =
 
 The 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.
 
-=== Command-line parameters ===
+== Command-line parameters ==
 
 To execute a program and trace it, type
@@ -28 +28 @@
 }}}
 
-=== Keyboard controls ===
+== Keyboard controls ==
 
 Press 'Q' anytime to quit the tracing application.
 
-=== Understanding the output ===
+== Understanding the output ==
 
 A typical application-protocol message has the form:
@@ -46 +46 @@
 Here ''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).
 
-=== Notes ===
+== Notes ==
 
  * 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!