Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1815187[details]
c file trigger the report
Description of problem:
Given C file triggers a report which is technically possible, but irrelevant in practise.
The bug to trigger depends on the func1 function to be called twice and the ++ptr manipulation inside. The analyzer assumes this _could_ overflow to NULL and hit a NULL pointer deref in the final return statement.
Version-Release number of selected component (if applicable):
gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-2)
How reproducible:
always
Steps to Reproduce:
1. gcc -fanalyzer attachment.c
Actual results:
see second attachment
Expected results:
no error
Upstream status:
Fixed upstream on trunk (for GCC 12) on 2021-08-23 in r12-3094-ge82e0f149b0aba660896ea9aa12c442c07a16d12
Fixed upstream on releases/gcc-11 branch on 2021-12-10 in r11-9374-gde0656f98640a57cd9dfdb090264afaa06ba46cc
This fix is *not* in the upstream gcc 11.2 release (which was tagged on 2021-07-28)
I don't plan to backport the fix to gcc 10 (too much has changed within the analyzer)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (new packages: gcc), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:3966
Created attachment 1815187 [details] c file trigger the report Description of problem: Given C file triggers a report which is technically possible, but irrelevant in practise. The bug to trigger depends on the func1 function to be called twice and the ++ptr manipulation inside. The analyzer assumes this _could_ overflow to NULL and hit a NULL pointer deref in the final return statement. Version-Release number of selected component (if applicable): gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-2) How reproducible: always Steps to Reproduce: 1. gcc -fanalyzer attachment.c Actual results: see second attachment Expected results: no error