Re: [Gtkwave-users] RE : best trace format for kernel tracer

[<by...@nc...>]

I just checked the appropriate fix into SVN for fst.c.

Note that vcd2fst doesn't support those as they're not a legitimate value in VCD and are gtkwave extensions. (I don't want to slow down vcd2fst unless I have to.)  For your external writer you should be ok.

-Tony


---- Matthieu Castet <mat...@pa...> wrote: 
> Hi,
> 
> > Try using FST.  Again, don't put spaces in signal names.
> 
> Thanks for your reply.
> 
> After some tests, it seems fst only support "xz01" bit state. [1]
> 
> Only vcd format seems to support u and w state.
> 
> Matthieu
> 
> [1]
> 
>                 case '0':   h_val = AN_0; break;
>                 case '1':   h_val = AN_1; break;
>                 case 'Z':
>                 case 'z':   h_val = AN_Z; break;
>                 default:    h_val = AN_X; break;