https://bugs.kde.org/show_bug.cgi?id=487862
--- Comment #9 from Mark Wielaard <m...@klomp.org> --- Hi John, (In reply to John Reiser from comment #8) > What has changed is very large apps such as qemu-user-* which depend on > dozens of "random" libraries, and the system > builders/maintainers/administrators > who tired of their own version of "dll hell" due to dependency tracking, > and the users (including "systematic" users with scripts) who got tired of > multi-second initialization of all those shared libraries; all gained new > appreciation > for -static builds of ET_EXEC (no shared libraries at all!) which > initialize in a flash > and have robust configuration (none!) for end users. Disk space is cheap > for many > such users; time is not. qemu-user has grown into a predictable evolution > which > avoids nearly all "security" incidents which otherwise might argue for using > shared libraries. Interesting, but is this still about how to handle the brk syscall? It sound like a separate issue that valgrind doesn't support static linked binaries (because we cannot use the LD_PRELOAD trick to get our alternative malloc/mem/str implementations loaded). There seem to be some alternate bugs about that. https://bugs.kde.org/show_bug.cgi?id=198248 https://bugs.kde.org/show_bug.cgi?id=406434 -- You are receiving this mail because: You are watching all bug changes.
