parser-gcc: fix parsing of UBSAN reports with missing function names #184
Conversation
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
lzaoral
force-pushed
the
ubsan-parser-no-fnc
branch
from
195b6c2 to
e06fe88
Compare
kdudka
requested changes
May 27, 2024
There was a problem hiding this comment.
The new test-case needs to be registered at
csdiff/tests/csgrep/CMakeLists.txt
Line 170 in 43ae09a
|
@kdudka I have amended an existing testcase that focuses on parsing of UBSAN backtraces so that should not be necessary. |
lzaoral
force-pushed
the
ubsan-parser-no-fnc
branch
from
e06fe88 to
9c716e3
Compare
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.
No description provided.