-
Notifications
You must be signed in to change notification settings - Fork 445
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
SEGFAULT in p4c-bm2-ss (P4::CallGraph<...>::strongConnect) #185
Comments
This program #includes a file which is not available. In the absence of this file the program does not crash. |
Good catch. It appears the SEGFAULT occurs for unrecognized include files. Changing the include to:
also triggers the crash. |
Can you assign this bug to @ChrisDodd please? |
Also, the errors from the preprocessor are not relayed to the user - so the user does not know what the problems are. |
This just gives me:
which is somewhat unclear (should be copying the preprocessor error message), but not incorrect... |
The fact that the preprocessor error message is not relayed to the user is a bug in itself. |
Without the >/dev/null we get spurious warning messages from the preprocessor (sometimes), which cause other problems. |
The problem was with newlines in strings. |
I believe that this issue has been solved. |
Attempting to compile the attached P4_14 program with
p4c-bm2-ss
results in a SEGFAULT.Program: repeater.txt
Command:
Stack trace:
The text was updated successfully, but these errors were encountered: