Handle source paths starting with at sign#4845
Merged
Merged
Conversation
Rahmi-serag
force-pushed
the
fix/4658-at-folder-path
branch
from
307d0c4 to
ece91b4
Compare
bruntib
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #4658.
CodeChecker treated every command argument starting with @ as a response file. Because of that, a real source path like @folder/main.cpp was incorrectly interpreted as folder/main.cpp.
This change keeps @... as a normal compiler argument when that path exists as a real file.
Added a unit test for source file paths starting with @.
Tested with:
REPO_ROOT="$PWD" PYTHONPATH="$PWD/analyzer:$PWD/build/CodeChecker/lib/python3:$PWD" pytest -q analyzer/tests/unit/test_log_parser.py