|
From: rajesh s. <inf...@gm...> - 2018-11-19 11:10:41
|
Hi All, I were trying to compile valgrind using cavium toolchain 64 bit for mips architecture. I am using below configuration option to configure and while compilation getting below error. Could plz hel me to resolve this compilation issue. ./configure --host=mips64-linux-gnu CC=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-gcc CXX=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-g++ --prefix=/home/rajesh/Valgrind/valgrind_bins --exec-prefix=/home/rajesh/Valgrind/valgrind_bins --target=x86_64-linux-gnu Error message while compiling: /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: valgrind-launcher-linux.o: uses different e_flags (0x200) fields than previous modules (0x0) /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: failed to merge target specific data of file valgrind-launcher-linux.o /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: valgrind-m_debuglog.o: uses different e_flags (0x200) fields than previous modules (0x0) /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: failed to merge target specific data of file valgrind-m_debuglog.o collect2: error: ld returned 1 exit status Makefile:2804: recipe for target 'valgrind' failed make[3]: *** [valgrind] Error 1 make[3]: Leaving directory '/home/rajesh/Valgrind/valgrind-3.14.0/coregrind' Makefile:1901: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/home/rajesh/Valgrind/valgrind-3.14.0/coregrind' Makefile:835: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/rajesh/Valgrind/valgrind-3.14.0' Makefile:704: recipe for target 'all' failed make: *** [all] Error 2 rajesh@rajesh-dt:~/Valgrind/valgrind-3.14.0$ Thanks, Rajesh |
|
From: Aleksandar R. <ale...@rt...> - 2018-11-19 14:24:24
|
Hi, Have you tried to specify CFLAGS ? eg. ./configure --host=mips64-linux-gnu CC=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-gcc CXX=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-g++ --prefix=/home/rajesh/Valgrind/valgrind_bins --exec-prefix=/home/rajesh/Valgrind/valgrind_bins --target=x86_64-linux-gnu*CFLAGS="-march=octeon2 -mabi=64"* Can you provide config.log ? Regards, Aleksandar On 11/19/2018 12:10 PM, rajesh singh wrote: > > Hi All, > > I were trying to compile valgrind using cavium toolchain 64 bit for > mips architecture. I am using below configuration option to configure > and while compilation getting below error. Could plz hel me to resolve > this compilation issue. > > ./configure --host=mips64-linux-gnu > CC=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-gcc > CXX=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-g++ > --prefix=/home/rajesh/Valgrind/valgrind_bins > --exec-prefix=/home/rajesh/Valgrind/valgrind_bins > --target=x86_64-linux-gnu > > Error message while compiling: > > /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: > valgrind-launcher-linux.o: uses different e_flags (0x200) fields than > previous modules (0x0) > /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: > failed to merge target specific data of file valgrind-launcher-linux.o > /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: > valgrind-m_debuglog.o: uses different e_flags (0x200) fields than > previous modules (0x0) > /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: > failed to merge target specific data of file valgrind-m_debuglog.o > collect2: error: ld returned 1 exit status > Makefile:2804: recipe for target 'valgrind' failed > make[3]: *** [valgrind] Error 1 > make[3]: Leaving directory > '/home/rajesh/Valgrind/valgrind-3.14.0/coregrind' > Makefile:1901: recipe for target 'all' failed > make[2]: *** [all] Error 2 > make[2]: Leaving directory > '/home/rajesh/Valgrind/valgrind-3.14.0/coregrind' > Makefile:835: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/home/rajesh/Valgrind/valgrind-3.14.0' > Makefile:704: recipe for target 'all' failed > make: *** [all] Error 2 > rajesh@rajesh-dt:~/Valgrind/valgrind-3.14.0$ > > Thanks, > Rajesh > > > > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: rajesh s. <inf...@gm...> - 2018-11-21 06:34:18
|
Hi Aleksandar, Thanks for your support. I compiled the valgrind and loaded the valgrind file and on node with all supporting files. I ran the valgrin with my program but not getting the proper output. Can you plz help on it ? -bash-4.3# -bash-4.3# /etc/bin/valgrind --tool=memcheck --leak-check=full -v /etc/bin/switch.d ==1658== Memcheck, a memory error detector ==1658== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1658== Using Valgrind-3.14.0-353a3587bb-20181007X and LibVEX; rerun with -h for copyright info ==1658== Command: /etc/bin/switch.d ==1658== --1658-- Valgrind options: --1658-- --tool=memcheck --1658-- --leak-check=full --1658-- -v --1658-- Contents of /proc/version: --1658-- Linux version 3.10.85-LINUX_3_10_85_SSBC_0_0_4 (anilkumar@anilkumar-dt) (gcc version 4.7.0 (Cavium Inc. Version: SDK_BUILD build 44) ) #1 Wed Jul 25 12:43:16 IST 2018 --1658-- --1658-- Arch and hwcaps: MIPS64, BigEndian, Cavium-baseline --1658-- Page sizes: currently 4096, max supported 65536 --1658-- Valgrind library directory: /tmp/bin/lib/home/rajesh/Valgrind/valgrind_bins/lib/valgrind/ --1658-- Reading syms from /lib64/ld-2.16.so --1658-- Reading syms from /etc/bin/switch.d --1658-- Reading syms from /var/tmp/bin/lib/home/rajesh/Valgrind/valgrind_bins/lib/valgrind/memcheck-mips64-linux --1658-- object doesn't have a dynamic symbol table --1658-- Scheduler: using generic scheduler lock implementation. --1658-- Reading suppressions file: /tmp/bin/lib/home/rajesh/Valgrind/valgrind_bins/lib/valgrind//default.supp ==1658== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-1658-by-root-on-??? ==1658== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-1658-by-root-on-??? ==1658== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-1658-by-root-on-??? ==1658== ==1658== TO CONTROL THIS PROCESS USING vgdb (which you probably ==1658== don't want to do, unless you know exactly what you're doing, ==1658== or are doing some strange experiment): ==1658== /tmp/bin/lib/home/rajesh/Valgrind/valgrind_bins/lib/valgrind//../../bin/vgdb --pid=1658 ...command... ==1658== ==1658== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==1658== /path/to/gdb /etc/bin/switch.d ==1658== and then give GDB the following command ==1658== target remote | /tmp/bin/lib/home/rajesh/Valgrind/valgrind_bins/lib/valgrind//../../bin/vgdb --pid=1658 ==1658== --pid is optional if only one valgrind process is running ==1658== --1658-- REDIR: 0x401ce00 (ld.so.1:strlen) redirected to 0x5810fdd4 (vgPlain_mips64_linux_REDIR_FOR_strlen) --1658-- REDIR: 0x401ca80 (ld.so.1:index) redirected to 0x5810fdb0 (vgPlain_mips64_linux_REDIR_FOR_index) --1658-- Reading syms from /var/tmp/bin/lib/home/rajesh/Valgrind/valgrind_bins/lib/valgrind/vgpreload_core-mips64-linux.so --1658-- Reading syms from /var/tmp/bin/lib/home/rajesh/Valgrind/valgrind_bins/lib/valgrind/vgpreload_memcheck-mips64-linux.so --1658-- REDIR: 0x401d930 (ld.so.1:mempcpy) redirected to 0x4051268 (mempcpy) --1658-- REDIR: 0x401d2e0 (ld.so.1:bcmp) redirected to 0x404f878 (bcmp) --1658-- REDIR: 0x401da40 (ld.so.1:memcpy) redirected to 0x404e878 (memcpy) --1658-- Reading syms from /lib64/libstdc++.so.6.0.17 --1658-- Reading syms from /etc/bin/software/sharedobj/libboard.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libDaemonCtlClient.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libDaemonCtl.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libERPIfaceServerSocketStub.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libERPIfaceClientSocketStub.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libERPIfaceSocket.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libthreadlib.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libsockIf.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libconnV2.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/libcommonUtils.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /etc/bin/software/sharedobj/liblibLite.so --1658-- object doesn't have a symbol table --1658-- Reading syms from /lib64/librt-2.16.so --1658-- Reading syms from /lib64/libm-2.16.so --1658-- Reading syms from /lib64/libpthread-2.16.so --1658-- Reading syms from /lib64/libdl-2.16.so --1658-- Reading syms from /lib64/libc-2.16.so --1658-- Reading syms from /lib64/libgcc_s.so.1 ==1658== Invalid write of size 1 ==1658== at 0x4709044: __pthread_initialize_minimal (in /lib64/ libpthread-2.16.so) ==1658== by 0x4707A58: ??? (in /lib64/libpthread-2.16.so) ==1658== Address 0xffffffffffff8d12 is not stack'd, malloc'd or (recently) free'd ==1658== ==1658== ==1658== Process terminating with default action of signal 10 (SIGBUS) ==1658== at 0x4709044: __pthread_initialize_minimal (in /lib64/ libpthread-2.16.so) ==1658== by 0x4707A58: ??? (in /lib64/libpthread-2.16.so) ==1658== Invalid read of size 4 ==1658== at 0x4019508: __dl_runtime_resolve (in /lib64/ld-2.16.so) ==1658== by 0x40192D8: _dl_runtime_resolve (in /lib64/ld-2.16.so) ==1658== Address 0xffffffffffff8900 is not stack'd, malloc'd or (recently) free'd ==1658== ==1658== ==1658== Process terminating with default action of signal 10 (SIGBUS) ==1658== at 0x4019508: __dl_runtime_resolve (in /lib64/ld-2.16.so) ==1658== by 0x40192D8: _dl_runtime_resolve (in /lib64/ld-2.16.so) ==1658== ==1658== HEAP SUMMARY: ==1658== in use at exit: 0 bytes in 0 blocks ==1658== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==1658== ==1658== All heap blocks were freed -- no leaks are possible ==1658== ==1658== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) ==1658== ==1658== 1 errors in context 1 of 2: ==1658== Invalid read of size 4 ==1658== at 0x4019508: __dl_runtime_resolve (in /lib64/ld-2.16.so) ==1658== by 0x40192D8: _dl_runtime_resolve (in /lib64/ld-2.16.so) ==1658== Address 0xffffffffffff8900 is not stack'd, malloc'd or (recently) free'd ==1658== ==1658== ==1658== 1 errors in context 2 of 2: ==1658== Invalid write of size 1 ==1658== at 0x4709044: __pthread_initialize_minimal (in /lib64/ libpthread-2.16.so) ==1658== by 0x4707A58: ??? (in /lib64/libpthread-2.16.so) ==1658== Address 0xffffffffffff8d12 is not stack'd, malloc'd or (recently) free'd ==1658== ==1658== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) Bus error -bash-4.3# Thanks, Rajesh On Mon, Nov 19, 2018 at 2:47 PM rajesh singh <inf...@gm...> wrote: > Hi Aleksandar, > > Thanks for your support. > I tried with *CFLAGS="-march=octeon2 -mabi=64" and now it's compiled * > *successfully**.* > > > Again thanks lot for your support. > > Thanks & Regards, > Rajesh > > On Mon, Nov 19, 2018 at 7:55 PM Aleksandar Rikalo < > ale...@rt...> wrote: > >> Hi, >> >> Have you tried to specify CFLAGS ? >> eg. >> ./configure --host=mips64-linux-gnu >> CC=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-gcc >> CXX=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-g++ >> --prefix=/home/rajesh/Valgrind/valgrind_bins >> --exec-prefix=/home/rajesh/Valgrind/valgrind_bins --target=x86_64-linux-gnu *CFLAGS="-march=octeon2 >> -mabi=64"* >> >> Can you provide config.log ? >> >> Regards, >> Aleksandar >> >> >> On 11/19/2018 12:10 PM, rajesh singh wrote: >> >> Hi All, >> >> I were trying to compile valgrind using cavium toolchain 64 bit for mips >> architecture. I am using below configuration option to configure and while >> compilation getting below error. Could plz hel me to resolve this >> compilation issue. >> >> ./configure --host=mips64-linux-gnu >> CC=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-gcc >> CXX=/opt/CAVIUMsdk312/OCTEON-SDK/tools/bin/mips64-octeon-linux-gnu-g++ >> --prefix=/home/rajesh/Valgrind/valgrind_bins >> --exec-prefix=/home/rajesh/Valgrind/valgrind_bins --target=x86_64-linux-gnu >> >> Error message while compiling: >> >> /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: >> valgrind-launcher-linux.o: uses different e_flags (0x200) fields than >> previous modules (0x0) >> /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: >> failed to merge target specific data of file valgrind-launcher-linux.o >> /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: >> valgrind-m_debuglog.o: uses different e_flags (0x200) fields than previous >> modules (0x0) >> /opt/CAVIUMsdk312/OCTEON-SDK/tools-gcc-4.7/bin/../lib/gcc/mips64-octeon-linux-gnu/4.7.0/../../../../mips64-octeon-linux-gnu/bin/ld: >> failed to merge target specific data of file valgrind-m_debuglog.o >> collect2: error: ld returned 1 exit status >> Makefile:2804: recipe for target 'valgrind' failed >> make[3]: *** [valgrind] Error 1 >> make[3]: Leaving directory >> '/home/rajesh/Valgrind/valgrind-3.14.0/coregrind' >> Makefile:1901: recipe for target 'all' failed >> make[2]: *** [all] Error 2 >> make[2]: Leaving directory >> '/home/rajesh/Valgrind/valgrind-3.14.0/coregrind' >> Makefile:835: recipe for target 'all-recursive' failed >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory '/home/rajesh/Valgrind/valgrind-3.14.0' >> Makefile:704: recipe for target 'all' failed >> make: *** [all] Error 2 >> rajesh@rajesh-dt:~/Valgrind/valgrind-3.14.0$ >> >> Thanks, >> Rajesh >> >> >> >> >> _______________________________________________ >> Valgrind-developers mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/valgrind-developers >> >> >> _______________________________________________ >> Valgrind-developers mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-developers >> > |