Project

General

Profile

Trace Format » History » Version 1

Sergey Smolov, 09/18/2018 04:29 PM

1 1 Sergey Smolov
h1. Trace Format
2
3
QEMU4V is able to generate traces of program execution. Here is the description of the trace format.
4
The QEMU4V trace contains records of the following kinds: instruction records, memory access records, register write records.
5
6
h2. Instruction record
7
8
Appears in the trace when the corresponding instruction from the target program has been executed.
9
The record format is as follows:
10
<pre><code class="text">
11
<time> <scale> <cpu> [IT|IS] (<inst_id>) <addr> <opcode> [A|T|X] <mode>_<security> : <disasm>
12
</code></pre>
13
The record fields are described in the following table:
14
| *Field* | Timestamp | *Value* |
15
| <time> | *Description* | Integer |
16
| <scale> | *Description* | *Value* |
17
| <cpu> | *Description* | *Value* |
18
| [IT<nowiki>|</nowiki>IS] | *Description* | *Value* |
19
| <inst_id> | *Description* | *Value* |
20
| <addr> | *Description* | *Value* |
21
| <opcode> | *Description* | *Value* |
22
| [A|T|X] | *Description* | *Value* |
23
| <mode> | *Description* | *Value* |
24
| <security> | *Description* | *Value* |
25
| <disasm> | *Description* | *Value* |