[valgrind] [Bug 465916] Valgrind crashing with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=465916 Paul Floyd changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Paul Floyd --- You should also be able to run Valgrind from your build directory with ./vg-in-place Your crash is quite early in Valgrind startup. I don't use android at all so I can't help much. Can you debug Valgrind as per the instructions in README_DEVELOPERS? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465916] Valgrind crashing with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=465916 --- Comment #4 from ramesh k --- 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.
[valgrind] [Bug 465916] Valgrind crashing with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=465916 --- Comment #3 from ramesh k --- Sorry for late response. Please find the log with -d option lahaina:/data/local/tmp/ramesh/Inst/data/local/Inst/bin # ./valgrind -d --help --10869:1:debuglog DebugLog system started by Stage 1, level 1 logging requested --10869:1:launcher no tool requested, defaulting to 'memcheck' --10869:1:launcher no client specified, defaulting platform to 'arm64-linux' --10869:1:launcher launching /data/local/tmp/ramesh/data/local/Inst/libexec/valgrind/memchSegmentation fault 139|lahaina:/data/local/tmp/ramesh/Inst/data/local/Inst/bin # -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465916] Valgrind crashing with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=465916 Paul Floyd changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Paul Floyd --- Reminder -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465916] Valgrind crashing with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=465916 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- Can you post the output? Do verbose/debug options help (like -d -d -d -v -v -v)? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465916] Valgrind crashing with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=465916 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
