8000 Using a scalar value change for a vector var causes segfault · Issue #434 · gtkwave/gtkwave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Using a scalar value change for a vector var causes segfault #434

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you ag 7D4C ree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
rfuest opened this issue May 4, 2025 · 0 comments
Open

Using a scalar value change for a vector var causes segfault #434

rfuest opened this issue May 4, 2025 · 0 comments

Comments

@rfuest
Copy link
Collaborator
rfuest commented May 4, 2025

Trying to use a scalar vector change in a VCD file to update the value of a vector var causes a segfault in GTKWave LTS, when the trace is added:

$var wire 2 a var[0:1] $end
$enddefinitions $end
#0
0a
#1
1a
#2

This example is clearly an invalid VCD file, but I discovered this when I worked on 1 bit vectors, where VCD writers might inconsistently either use scalar or vector value changes:

$var wire 1 a var[0:0] $end
$enddefinitions $end
#0
0a
$comment or: $end
b0 a

GTKWave LTS should be fine in this case, because it treats the variable as a scalar and not a vector and both types of value change statement seem to work. For GTKWave 4 I'm planning to ignore scalar value changes for any variable that isn't a scalar or a 1 bit wide vector and print a warning.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rfuest
0