Skip to content
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

DO NOT MERGE; practical example of how gcc -fanalyzer works #1261

Conversation

jiridanek
Copy link
Contributor

No description provided.

@jiridanek jiridanek self-assigned this Oct 15, 2023
@@ -288,6 +288,8 @@

int main(int argc, char **argv)
{
char *buf = malloc(42);
buf[6] = '7';

Check warning

Code scanning / GNU C11

dereference of possibly-NULL 'buf' Warning

dereference of possibly-NULL 'buf'
@codecov
Copy link

codecov bot commented Oct 15, 2023

Codecov Report

Merging #1261 (ad0f844) into main (3d81fb8) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1261      +/-   ##
==========================================
- Coverage   78.41%   78.30%   -0.11%     
==========================================
  Files         246      246              
  Lines       63516    63517       +1     
  Branches     5872     5872              
==========================================
- Hits        49805    49738      -67     
- Misses      11079    11114      +35     
- Partials     2632     2665      +33     
Flag Coverage Δ
pysystemtests 87.69% <ø> (-0.07%) ⬇️
pyunittests 54.60% <ø> (ø)
systemtests 72.27% <100.00%> (-0.13%) ⬇️
unittests 26.52% <0.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
calculator 30.06% <0.00%> (-0.02%) ⬇️
systemtests 78.92% <100.00%> (-0.10%) ⬇️

@jiridanek
Copy link
Contributor Author

Effectiveness of -fanalyzer has been proven.

My chosen approach for running clang-analyzer unfortunately does not seem to provide SARIF outputs and they cannot be obtained easily.

@jiridanek jiridanek closed this Oct 19, 2023
@jiridanek jiridanek deleted the jd_2023_10_15_introduce_bug_fanalyzer branch October 19, 2023 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant