-
-
Notifications
You must be signed in to change notification settings - Fork 84
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.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expression coverage assertion crash + follow-up crash related to PSL #1150
Comments
Even the second crash seems to be somehow related to the coverage. If I re-elaborate without the coverage
|
nickg
added a commit
that referenced
this issue
Feb 1, 2025
nickg
added a commit
that referenced
this issue
Feb 2, 2025
Both of these should be fixed now, thanks. |
Thanks for fixing this so quickly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I have encountered another issue when porting large TB to NVC. When I enable expression coverage,
and build in the debug mode, I get crash during elaboration.
To reproduce:
I get crash:
When I added hierarchy prints into the code, it seems to have problem at if condition expression in
src/can_top_level.vhd
:Though if I remove this process (just as a hack an try to continue), I get similar crash at e.g. following logic:
in
src/bus_sampling/bit_err_detector.vhd
.I tried to add prints just before the assertion failure, but I don't get the full log well printed.
When printing the
tree_kind
with the debug disabled (not to get the crash), I getT_PROT_FCALL
,so maybe it is as simple as extending the assertion for another allowed
tree_kind_t
in it.I don't know.
When I try to extend the assertion to have
T_PROT_FCALL
allowed, I elaborate OK, but I crash at runtime(due to different issue in a PSL cover directive):
The text was updated successfully, but these errors were encountered: