Linux Secret Memory "secretmemfd" System Call Remains Under Review

[programmerjake]

Debugging requires a debug build, which has a tremendous amount of additional hooks and whatnot, which is why it is also so important to be careful not to ship debug builds by mistake.

that's incorrect -- you can debug a release build, though if you can't get the corresponding DWARF debugging information then you better be good at reading assembly language! Even if you have the debugging information, the compiler's optimizations often reorder, delete, and otherwise adjust the code, making it harder to debug.

[milkylainen]

Yes. I can't at all foresee bad software making life a bitch with all the nice ways to avoid introspection built in already.

[pal666]

Umm, isn't process mapped memory only visible to that process the default, and if not, why isn't it?

no, it's always visible to kernel. and kernel could be exploited

[pal666]

Debugging requires a debug build

not really

[DrYak]

Debugging requires a debug build,

(Me, having a day cheating on Android freemium games using GDB): Nope, definitely not. You can definitely use GDB with a release build.