https://bugs.kde.org/show_bug.cgi?id=406349
Samuel Bronson <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Samuel Bronson <[email protected]> --- Just to clarify: this warning always prints the full set of flags found in the DT_FLAGS_1 entry, including the supported ones, from its introduction at <https://cs.android.com/android/_/android/platform/bionic/+/6cdeb5234d7f4523fe9d83974f265d80f10512a6:linker/linker.cpp;drc=6cdeb5234d7f4523fe9d83974f265d80f10512a6;l=2067> to its current version at <https://cs.android.com/android/_/android/platform/bionic/+/7ea4c99263fb09c4590135e78bc26fa4e5786083:linker/linker.cpp;drc=7ea4c99263fb09c4590135e78bc26fa4e5786083;l=3186>. The actual set of supported flags seems to range from `DF_1_NOW | DF_1_GLOBAL` to `DF_1_NOW | DF_1_GLOBAL | DF_1_NODELETE | DF_1_PIE | DF_1_ORIGIN`. In any case, since `DF_1_INTERPOSE` and `DF_1_INITFIRST` never "worked" on Android, the warning is presumably unrelated to any regressions you're encountering with leak tracking. Actually, there's an FAQ entry titled "Memcheck doesn't report any errors and I know my program has errors." at <https://valgrind.org/docs/manual/faq.html#faq.hiddenbug>; it seems likely that your issue was caused by statically linking libc or libc++ into your test program? -- You are receiving this mail because: You are watching all bug changes.
