gtkwave - Visualization tool for VCD, LXT, and VZT files

gtkwave [option]... [DUMPFILE] [SAVEFILE] [RCFILE]

Visualization tool for VCD, LXT, LXT2, VZT, and GHW. VCD is an industry standard simulation dump format. LXT, LXT2, and VZT have been designed specifically for use with gtkwave. GHW is the native VHDL format generated by GHDL. Native dumpers exist in Icarus Verilog for the LXT formats so conversion with vcd2lxt(1) or vcd2lxt2(1) is not necessary to take direct advantage of LXT with that simulator. AET2 files can also be processed provided that libae2rw is available but this is only of interest to people who use IBM EDA toolsets.

-n,--nocli <directory name> Use file requester for dumpfile name

-f,--dump <filename>

Specify dumpfile name.

-r,--rcfile <filename>

Specify override .gtkwaverc filename.

-i,--indirect <filename>

Specify indirect facs file name. The file contains a series of regular expressions used to limit what signals can be browsed. Signal names which match any of the regular expressions will be viewable. Typically, indirect files are used to reduce memory requirements for extremely large models containing millions of facilities or to strip out top-level hierarchy clutter from BugSpray models. This feature is only available with the AET2 loader.

-l,--logfile <filename>

Specify simulation logfile name. Multiple logfiles may be specified by preceeding each with the command flag. By selecting the numbers in the text widget, the marker will immediately zoom to the specific time value.

-d,--defaultskip

If there is not a .gtkwaverc file in the home directory or current directory and it is not explicitly specified on the command line, when this option is enabled, do not use an implicit configuration file and instead default to the old "whitescreen" behavior.

-s,--start <time>

Specify start time for LXT2/VZT block skip.

-e,--end <time>

Specify end time for LXT2/VZT block skip.

-c,--cpu <numcpus>

Specify number of CPUs available for parallelizable ops (e.g., block prefetching on VZT reads).

-v,--vcd

Use stdin as a VCD dumpfile.

-V,--version

Display version banner then exit.

-h,--help

Display help then exit.

-x,--exit

Exit after loading trace (for loader benchmarking).

~/.gtkwaverc

To run this program the standard way type:

gtkwave dumpfile.vcd

Alternatively you can run it with a save file as:

gtkwave dumpfile.vcd dumpfile.sav

Command line options are not necessary for representing the dumpfile, savefile, and rcfile names. They are merely provided to allow specifying them out of order. Note that on non-glibc systems, the long command line options will not be available and that the short ones will have to be used instead.

Anthony Bybell <bybell@nc.rr.com>

lxt2vcd(1) vcd2lxt(1) vcd2lxt2(1) vzt2vcd(1) vcd2vzt(1)