https://bugs.kde.org/show_bug.cgi?id=327427
--- Comment #4 from Mark Wielaard <m...@klomp.org> --- I had hoped the fix for Bug 79362 - Debug info is lost for .so files when they are dlclose'd, would have also fixed this issue. But it didn't. Note that this is a somewhat weird/special case, it happens with the following elfutils testcases (when configure with --enable-valgrind to run all tests under valgrind): tests/run-backtrace-demangle.sh tests/run-stack-d-test.sh tests/run-stack-demangled-test.sh tests/run-stack-i-test.sh They all have the following workaround for now: # Disable valgrind while dumping because of a bug unmapping libc.so. # https://bugs.kde.org/show_bug.cgi?id=327427 SAVED_VALGRIND_CMD="$VALGRIND_CMD" unset VALGRIND_CMD They are somewhat special in that try to create a backtrace for a different process, so they map (and unmap) libc.so into their address space twice (once because they are linked against it themselves and then another time because the target process is linked against it). Normal processes would obviously never do that. -- You are receiving this mail because: You are watching all bug changes.
