-
Notifications
You must be signed in to change notification settings - Fork 2
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
Core dumped on an undefined variable with a new PC definition #4
Comments
Hi, I checked out the commit ba43fe1 - which is the last commit in 2014 (= oldversion), and I can't reproduce your issue. Even with the latest commit (bc34eb3), I get the desired error message. |
OK, so I still get a segmentation fault on ba43fe1 just as described:
Interestingly it doesn't show up under
However after fetching just the very next commit 98c93ba everything works as expected:
Judging from the contents of a core dump, it looks like the issue has been indeed fixed by 98c93ba:
No clue why you couldn't reproduce the problem. I'm glad it's been fixed though. |
Yep, it seems fixed in latest commits - and your're right, the bug is still in ba43fe1. |
When an undefined variable is encountered in a source code accompanied by an additional PC definition command, it results in a failed assertion and a consequent core dump.
Here is a minimal example to reproduce the issue:
Compilation of this syntactically valid code snippet fails with the following error message:
An expected behaviour would be to report
show
as an undefined variable just like this:The text was updated successfully, but these errors were encountered: