https://bugs.kde.org/show_bug.cgi?id=446123
--- Comment #2 from Tulio Magno Quites Machado Filho <tul...@quites.com.br> --- Notice that glibc 2.35 changed the behavior of backtrace and this issue should not happen anymore. Anyway, the lack of vdso causes a difference of behavior when running on top valgrind versus outside of valgrind making it very hard to use valgrind to detect issues in those scenarios. So what I mean is: even with glibc 2.35 there is still value in providing the VDSO. -- You are receiving this mail because: You are watching all bug changes.
