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
parameter tracing support causes internal error #722
Comments
Original Redmine Comment I haven't found this bug yet, but added --no-trace-params as a flag to the git version. |
Original Redmine Comment Wilson: I just ran across this bug as well and figured out a way to make it go away without using --no-trace-params. I can probably provide you with a very trivial example that reproduces the issue. It's not clear from your response if you are not able to track it down because you can't reproduce it or you are able to reproduce it but just can't figure it out yet. If you can't reproduce it let me know and I should be able to send you a simple example. I'm using v3.862. |
Original Redmine Comment Here is a very trivial example to reproduce the issue. I hope it's helpful... |
Original Redmine Comment The test case was exactly what was needed. Fixed in git towards 3.863. |
Original Redmine Comment In 3.864. |
Author Name: Jie Xu (@jiexu)
Original Redmine Issue: 722 from https://www.veripool.org
Original Date: 2014-03-12
Original Assignee: Wilson Snyder (@wsnyder)
The error is "internal error: .., ../V3Task.cpp:1043: func ref not under scope".
The error is generated at the place where a localparam is defined with value calculated using task.
Sorry I am not able to reproduce this error with a simple test case. But the error disappear if I remove the commit "add parameters into trace files, #�"
The text was updated successfully, but these errors were encountered: