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
Verilator segfaults in V3Gate warning #911
Comments
Original Redmine Comment Hi, looked into both of your debug info files. The errors happen at in V3Gate.cpp where it tries to generate SYNCASYNCNET warning. To me the reason it happens is that the node it try to find is already deleted in a earlier stage. It would nice to share your altera_avalon_mm_clock_crossing_bridge.v or at least the part with warnings. Also when you have the callback from the debugger, go back to the frame of GateVisitor::warnSignals() and check which signal is the problem. You can find a GDB script file verilator source src/.gdbinit where some function are defined to check the node. But I don't know if you can do something similar in LLDB. |
Original Redmine Comment Hi, We do not get a segfault, when using the verilator_bin_dbg, there we retrieve proper warnings and are able to detect the signal causing this. However, when using plain verilator_bin it segfaults. I was able to do a detailed traceback after compiling with ```-g -O0
|
Original Redmine Comment Seems to me this is a clear error which should be reproducible on every run unless there are some different optimization options when calling Verilator. If my assumptions are correct, you can try the patch:
Basically I move the warning part before the optimizations in V3Gate where some nodes could be optimized out. |
Original Redmine Comment Thanks for patching, makes sense. Fixed in git towards 3.873. |
Original Redmine Comment In 3.874. |
Author Name: Eivind Liland
Original Redmine Issue: 911 from https://www.veripool.org
Original Date: 2015-04-24
Original Assignee: Jie Xu (@jiexu)
It happens unpredictably on various modules and with different versions of verilator (including the newest one). It varies from computer to computer and from session to session whether the problem occurs or not. (I would suspect that verilator is reading uninitialized memory?)
The problem occurs with different messages:
We've tried to create a reduced version of our sources, but haven't been successful so far because the error is hard to reproduce in a reliable way.
Attaching debug information
The text was updated successfully, but these errors were encountered: