Trace File: Formats and Statements



next up previous
Next: How to declare Up: No Title Previous: Setting of GUI

Trace File: Formats and Statements

The trace file must be a single file. The first line in the trace file should be:

<version-num> <max-proc-id>

The default version-num is 1. In order to change the value use

const version_num = <new-value>;

max-proc-id gives the maximum process identifier in the trace file.

The other entries in the trace file contains 7 fields.

<pid> <oid> <mtype> <mtag> <msize> <bpflag> <iflag>
where
  1. pid: process identifier where the event took place
  2. oid: identifier of any other process related to the event. For a Write event, this will be the identifier of the process where the message was sent. For a Read event, this will be the identifier of the process that sent the message.
  3. mtype: message type - Read, Write, Multicast, Other.
  4. mtag: user defined tag for the event.
  5. msize: size of the message. Can be 0 for non-communication events.
  6. bpflag: breakpoint flag
  7. iflag: used for instrumentation. If non-zero there are iflag number of additional attributes associated with the event. The user is supposed to notify Ariadne of additional attributes - their names, and the events they are attached to. If nothing is notified, the attributes are ignores.





Joydip Kundu