Closed ChillerDragon closed 4 days ago
Toolchain version? Is this a false positive?
Toolchain version?
LLVM (http://llvm.org/):
LLVM version 19.0.0git
Optimized build.
Is this a false positive?
I do not know. I somehow trust clang but haven't checked. Do you think it is a false positive? Then we can close it.
I somehow trust clang but haven't checked.
Please check before creating an issue.
Please check before creating an issue.
I create issues to check later. Or should I create those issues in my fork instead?
Reopend by https://github.com/ddnet/ddnet/pull/8327
Is this a lint we want to enable? What are the advantages and disadvantages?
I think checks for uninitialized memory are generally useful, some weird UI bug have been caused by uninitialized memory in the past and this can be hard to debug.
In this case it seems like a false-positive though. AFAICT the check assumes that the CMenus::CGhostItem
members m_aPlayer
, m_Failed
and m_Date
are uninitialized, but m_aPlayer
is initialized immediately after constructing the object and the other two variable are initialized in UpdateOwnGhost
.
However, the check in question, clang-analyzer-optin.cplusplus.UninitializedObject
, is already suppressed globally
https://github.com/ddnet/ddnet/blob/03b13cb9f51a343f61aac89c18bc5f7814a5e253/.clang-tidy#L3-L4
so it seems like we already decided to ignore this check at some point.
Okay I see. Unwanted lint and false positive. I would consider this issue solved.