-
Notifications
You must be signed in to change notification settings - Fork 274
goto-cc with command line option file #6592
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
Labels
Comments
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
Jan 19, 2022
GCC's doc says that options are separated by whitespace, with no particular significance of newlines. Therefore, process the entire file at once rather than line-by-line. Fixes: diffblue#6592
3 tasks
Thank you for your detailed report and the extra debugging already done! This issue will be fixed once #6595 has been merged. |
vmihalko
pushed a commit
to vmihalko/cbmc
that referenced
this issue
Jan 24, 2022
GCC's doc says that options are separated by whitespace, with no particular significance of newlines. Therefore, process the entire file at once rather than line-by-line. Fixes: diffblue#6592
vmihalko
pushed a commit
to vmihalko/cbmc
that referenced
this issue
Jan 24, 2022
GCC's doc says that options are separated by whitespace, with no particular significance of newlines. Therefore, process the entire file at once rather than line-by-line. Fixes: diffblue#6592
vmihalko
pushed a commit
to vmihalko/cbmc
that referenced
this issue
Jan 24, 2022
GCC's doc says that options are separated by whitespace, with no particular significance of newlines. Therefore, process the entire file at once rather than line-by-line. Fixes: diffblue#6592
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
CBMC version: 5.43.0 (cbmc-5.43.0)
Operating system: Linux
Exact command line resulting in the issue:
goto-cc @param
What behaviour did you expect:
goto-cc @param
should produce.gb
fileWhat happened instead:
goto-cc @param
givesError opening file ''
errorHi team,
I found that
goto-cc
is not able to parse command line option file correctly if all options/tokens are on different lines.For example, if I have a file named as
param
like this:Running
gcc @param
works fine, butgoto-cc @param
will giveError opening file ''
error.However, if I modify the
param
file to put all options/flags on the same line:or, only put
-o
andfile.gb
on the same line:In both cases,
goto-cc @param
works fine. This seems as a bug ifgoto-cc
is being used as a drop-in replacement ofgcc
in the build process. I wonder if this is a known issue or work-as-expected?Thanks!
The text was updated successfully, but these errors were encountered: