-
Notifications
You must be signed in to change notification settings - Fork 352
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
Parsing of the build.log fails when a command has \"\ #62
Comments
- Remove incorrect space escaping from ldlogger - Add quotation marks around arguments with spaces - Use shlex for splitting command line arguments Fixes Ericsson#62
@igalex Doesn't seem fix to me.
codechecker is failing with:
|
I have the same problem when I load the compile_commands.json generated by espressif/idf:v4.4.1. And I suspect it's because of those escape backslashes (\) ESP-IDF adds these \\\: Expanded section: I haven't tried it yet, but if single quotes solve the problem, with SED you could replace the \\\ by ' |
For example, the program that I am trying to build has this define:
-DDEFAULT_ICU_PLUGINS="/usr/local/lib/icu"\
Codechecker will fail this:
[ERROR] - The compile database is not valid.
[ERROR] - Invalid \escape: line 29848 column 786 (char 10574627)
The text was updated successfully, but these errors were encountered: