We got Uninitialized memory access when the program copies structures allocating them using new keyword.
Inside the actual structure there are some padding bytes. (I know we should design structures to avoid padding, but we have tons of legacy sources we don't have resource to refactor old codes.) I think this is false alarm, because the programnever accesses padding bytes when reads or writes the struct members. We should differentiate or filtersomehow this kid of problems from real uninitializes memory accesses.
Is there a way to do it?