https://bugs.kde.org/show_bug.cgi?id=465916
--- Comment #4 from ramesh k <r.kat...@samsung.com> --- I moved valgrind bin folder to different location and I am getting below log 139|lahaina:/data/local/Inst/bin # ./valgrind -d --help --12517:1:debuglog DebugLog system started by Stage 1, level 1 logging requested --12517:1:launcher no tool requested, defaulting to 'memcheck' --12517:1:launcher no client specified, defaulting platform to 'arm64-linux' --12517:1:launcher launching /data/local/Inst/libexec/valgrind/memcheck-arm64-linux --12517:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging requested --12517:1: main Welcome to Valgrind version 3.20.0 debug logging --12517:1: main Checking current stack is plausible --12517:1: main Checking initial stack was noted --12517:1: main Starting the address space manager --12517:1: main Address space manager is running --12517:1: main Starting the dynamic memory manager --12517:1:mallocfr newSuperblock at 0x1002001000 (pszB 4194272) owner VALGRIND/core --12517:1:mallocfr deferred_reclaimSuperblock at 0x1002001000 (pszB 4194272) (prev 0x0) oSegmentation fault -- You are receiving this mail because: You are watching all bug changes.
