[Gtkwave-users] best trace format for kernel tracer

[Matthieu C. <mat...@pa...>]

Hi,

we use gtkwave to display kernel event. Our current tools use lxt format but in
order to have better trace we need to add 2 states (u and w) to lxt by patching
gtkwave.

Now I wonder if it is possible to use another trace format so we don't have to
patch gtkwave.

We need :
- "01xzuw" bit state
- string
- integer
- float

Do you know a trace format that support that and that is not too complex to
generate ?

I wonder if VCD format support it. I tried to export our trace to vcd with
gtkwave. With the current it crash. With our patched version (3.2.0), the export
work, the the file is not readable [1].
Look like vcd format doesn't support space in signal name (and gtkwave export
doesn't remove them).


Matthieu


[1]
Near byte 649, $VAR parse error encountered
Near byte 686, $VAR parse error encountered
Near byte 721, $VAR parse error encountered
[...]