[Valgrind-users] [Help] I run test application throght the massif with --pages-as-heap, it failed. But I run the same application throught the massif with no --pages-as-heap, it is ok.why?

[Wuweijia <wuw...@hu...>]

The output as below:

localhost:/system/bin # LD_PRELOAD=/system/bin/linker64 ./valgrind --tool=massif -v  --pages-as-heap=yes  ./mcfPQ --gtest_filter=*DISTANCE_001_001*
==20333== Massif, a heap profiler
==20333== Copyright (C) 2003-2015, and GNU GPL'd, by Nicholas Nethercote
==20333== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==20333== Command: ./mcfPQ --gtest_filter=*DISTANCE_001_001*
==20333==
--20333-- Valgrind options:
--20333--    --tool=massif
--20333--    -v
--20333--    --pages-as-heap=yes
--20333-- Contents of /proc/version:
--20333--   Linux version 4.4.7+ (root@baixin-HP-Compaq-8200-Elite-MT-PC) (gcc version 4.9.3 20151223 (prerelease) (SDK V100R005C00SPC030B080) ) #1 SMP PREEMPT Fri Sep 9 14:57:05 CST 2016
--20333--
--20333-- Arch and hwcaps: ARM64, LittleEndian, baseline
--20333-- Page sizes: currently 4096, max supported 65536
--20333-- Valgrind library directory: /system/lib64/valgrind
--20333-- Massif: alloc-fns:
--20333-- Massif:   malloc
--20333-- Massif:   __builtin_new
--20333-- Massif:   operator new(unsigned)
--20333-- Massif:   operator new(unsigned long)
--20333-- Massif:   __builtin_vec_new
--20333-- Massif:   operator new[](unsigned)
--20333-- Massif:   operator new[](unsigned long)
--20333-- Massif:   calloc
--20333-- Massif:   realloc
--20333-- Massif:   memalign
--20333-- Massif:   posix_memalign
--20333-- Massif:   valloc
--20333-- Massif:   operator new(unsigned, std::nothrow_t const&)
--20333-- Massif:   operator new[](unsigned, std::nothrow_t const&)
--20333-- Massif:   operator new(unsigned long, std::nothrow_t const&)
--20333-- Massif:   operator new[](unsigned long, std::nothrow_t const&)
--20333-- Massif: ignore-fns:
--20333-- Massif:   <empty>
--20333-- Reading syms from /system/bin/mcfPQ
--20333-- Reading syms from /system/bin/linker64
--20333-- Reading syms from /system/lib64/valgrind/massif-arm64-linux
--20333--    object doesn't have a dynamic symbol table
--20333-- Scheduler: using generic scheduler lock implementation.
CANNOT LINK EXECUTABLE "./mcfPQ": can't read file "/system/lib64": Is a directory--------------------------why it link failed with -pages-as-heap ?  How can I resovle it ?
libc: CANNOT LINK EXECUTABLE "./mcfPQ": can't read file "/system/lib64": Is a directory
libc: Fatal signal 6 (SIGABRT), code -6 in tid 20333 (massif-arm64-li)
libc: Unable to open connection to debuggerd: Connection refused
--20333-- WARNING: unhandled arm64-linux syscall: 240
==20333==    at 0x40D8B80: __dl_syscall (syscall.S:44)
==20333==    by 0x4007397: __dl__ZL24debuggerd_signal_handleriP7siginfoPv (debugger.cpp:294)
==20333==    by 0x38088B8B: ??? (in /system/lib64/valgrind/massif-arm64-linux)
--20333-- You may be able to write your own handler.
--20333-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20333-- Nevertheless we consider this a bug.  Please report
--20333-- it at http://valgrind.org/support/bug_reports.html.
libc: failed to resend signal during crash: Function not implemented