|
From: David S. <drs...@gm...> - 2012-05-17 14:12:02
|
Hello Valgrind users, Please help me diagnose the following configure error on a x86_64/Linux system. I searched google for solutions, but found none. The error seems or originate in [gcc-version] in configure.in. Thanks! Dave [sunfire02:~/packages/valgrind-3.7.0] % $CC --version gcc4 (GCC) 4.6.0 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [sunfire02:~/packages/valgrind-3.7.0] % ./configure --prefix=/u/drsmith/local --with-mpicc=mpicc checking for a BSD-compatible install... /u/drsmith/local/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking whether ln -s works... yes checking for gcc... gcc4 checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc4 accepts -g... yes checking for gcc4 option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc4... gcc3 checking whether gcc4 and cc understand -c and -o together... yes checking how to run the C preprocessor... gcc4 -E checking whether we are using the GNU C++ compiler... yes checking whether g++4 accepts -g... yes checking dependency style of g++4... gcc3 checking for ranlib... ranlib checking for a sed that does not truncate output... /bin/sed checking for ar... /usr/bin/ar checking for perl... /usr/bin/perl checking for gdb... /usr/bin/gdb checking dependency style of gcc4... gcc3 checking for diff -u... yes checking for a supported version of gcc... no (4) configure: error: please use gcc >= 3.0 or clang >= 2.9 [sunfire02:~/packages/valgrind-3.7.0] % |
|
From: Tom H. <to...@co...> - 2012-05-17 14:29:41
|
On 17/05/12 15:13, David Smith wrote: > Please help me diagnose the following configure error on a x86_64/Linux system. I searched google for solutions, but found none. The error seems or originate in [gcc-version] in configure.in. Well it looks like there is something very odd about your compiler because although it is gcc 4 autoconf seems to think it is behaving like gcc 3 in various ways. What is the output of "gcc --version"? Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: Tom H. <to...@co...> - 2012-05-17 14:33:33
|
On 17/05/12 15:29, Tom Hughes wrote: > On 17/05/12 15:13, David Smith wrote: > >> Please help me diagnose the following configure error on a >> x86_64/Linux system. I searched google for solutions, but found none. >> The error seems or originate in [gcc-version] in configure.in. > > Well it looks like there is something very odd about your compiler > because although it is gcc 4 autoconf seems to think it is behaving like > gcc 3 in various ways. > > What is the output of "gcc --version"? Sorry, I see you already included that... Can you give the last few lines of config.log? Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: David S. <drs...@gm...> - 2012-05-17 14:41:16
|
Hi Tom, Thanks for looking at this. Here's gcc --version: [sunfire02:~/packages/valgrind-3.7.0] % gcc --version gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-51) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [sunfire02:~/packages/valgrind-3.7.0] % Note that $CC is set to gcc4 (previous message). Both gcc and gcc4 are valid commands in the search path. Here are "core tests" and the last lines in config.log: ## ----------- ## ## Core tests. ## ## ----------- ## configure:2510: checking for a BSD-compatible install configure:2578: result: /u/drsmith/local/bin/install -c configure:2589: checking whether build environment is sane configure:2639: result: yes configure:2780: checking for a thread-safe mkdir -p configure:2819: result: /bin/mkdir -p configure:2832: checking for gawk configure:2848: found /bin/gawk configure:2859: result: gawk configure:2870: checking whether make sets $(MAKE) configure:2892: result: yes configure:2974: checking whether to enable maintainer-specific portions of Makefiles configure:2983: result: no configure:3002: checking whether ln -s works configure:3006: result: yes configure:3061: checking for gcc configure:3088: result: gcc4 configure:3317: checking for C compiler version configure:3326: gcc4 --version >&5 gcc4 (GCC) 4.6.0 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3337: $? = 0 configure:3326: gcc4 -v >&5 Using built-in specs. COLLECT_GCC=gcc4 COLLECT_LTO_WRAPPER=/usr/pppl/gcc/4.6.0/libexec/gcc/x86_64-unknown-linux-gnu/4.6.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ./configure --prefix=/usr/pppl/gcc/4.6.0 --program-suffix=4 --with-mpc=/usr/pppl/mpc/0.9 --with-gmp=/usr/pppl/gmp/5.0.2 --with-mpfr=/usr/pppl/mpfr/3.0.1 Thread model: posix gcc version 4.6.0 (GCC) configure:3337: $? = 0 configure:3326: gcc4 -V >&5 gcc4: error: unrecognized option '-V' gcc4: fatal error: no input files compilation terminated. configure:3337: $? = 1 configure:3326: gcc4 -qversion >&5 gcc4: error: unrecognized option '-qversion' gcc4: fatal error: no input files compilation terminated. configure:3337: $? = 1 configure:3357: checking whether the C compiler works configure:3379: gcc4 -Wno-long-long conftest.c >&5 configure:3383: $? = 0 configure:3432: result: yes configure:3435: checking for C compiler default output file name configure:3437: result: a.out configure:3443: checking for suffix of executables configure:3450: gcc4 -o conftest -Wno-long-long conftest.c >&5 configure:3454: $? = 0 configure:3476: result: configure:3498: checking whether we are cross compiling configure:3506: gcc4 -o conftest -Wno-long-long conftest.c >&5 configure:3510: $? = 0 configure:3517: ./conftest configure:3521: $? = 0 configure:3536: result: no configure:3541: checking for suffix of object files configure:3563: gcc4 -c -Wno-long-long conftest.c >&5 configure:3567: $? = 0 configure:3588: result: o configure:3592: checking whether we are using the GNU C compiler configure:3611: gcc4 -c -Wno-long-long conftest.c >&5 configure:3611: $? = 0 configure:3620: result: yes configure:3629: checking whether gcc4 accepts -g configure:3649: gcc4 -c -g conftest.c >&5 configure:3649: $? = 0 configure:3690: result: yes configure:3707: checking for gcc4 option to accept ISO C89 configure:3771: gcc4 -c -Wno-long-long conftest.c >&5 configure:3771: $? = 0 configure:3784: result: none needed configure:3815: checking for style of include used by make configure:3843: result: GNU configure:3868: checking dependency style of gcc4 configure:3978: result: gcc3 configure:3994: checking whether gcc4 and cc understand -c and -o together configure:4025: gcc4 -c conftest.c -o conftest2.o >&5 configure:4029: $? = 0 configure:4035: gcc4 -c conftest.c -o conftest2.o >&5 configure:4039: $? = 0 configure:4050: cc -c conftest.c >&5 configure:4054: $? = 0 configure:4062: cc -c conftest.c -o conftest2.o >&5 configure:4066: $? = 0 configure:4072: cc -c conftest.c -o conftest2.o >&5 configure:4076: $? = 0 configure:4094: result: yes configure:4124: checking how to run the C preprocessor configure:4155: gcc4 -E conftest.c configure:4155: $? = 0 configure:4169: gcc4 -E conftest.c conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory compilation terminated. configure:4169: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "Valgrind" | #define PACKAGE_TARNAME "valgrind" | #define PACKAGE_VERSION "3.7.0" | #define PACKAGE_STRING "Valgrind 3.7.0" | #define PACKAGE_BUGREPORT "val...@li..." | #define PACKAGE_URL "" | #define PACKAGE "valgrind" | #define VERSION "3.7.0" | /* end confdefs.h. */ | #include <ac_nonexistent.h> configure:4194: result: gcc4 -E configure:4214: gcc4 -E conftest.c configure:4214: $? = 0 configure:4228: gcc4 -E conftest.c conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory compilation terminated. configure:4228: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "Valgrind" | #define PACKAGE_TARNAME "valgrind" | #define PACKAGE_VERSION "3.7.0" | #define PACKAGE_STRING "Valgrind 3.7.0" | #define PACKAGE_BUGREPORT "val...@li..." | #define PACKAGE_URL "" | #define PACKAGE "valgrind" | #define VERSION "3.7.0" | /* end confdefs.h. */ | #include <ac_nonexistent.h> configure:4368: checking for C++ compiler version configure:4377: g++4 --version >&5 g++4 (GCC) 4.6.0 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:4388: $? = 0 configure:4377: g++4 -v >&5 Using built-in specs. COLLECT_GCC=g++4 COLLECT_LTO_WRAPPER=/usr/pppl/gcc/4.6.0/libexec/gcc/x86_64-unknown-linux-gnu/4.6.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ./configure --prefix=/usr/pppl/gcc/4.6.0 --program-suffix=4 --with-mpc=/usr/pppl/mpc/0.9 --with-gmp=/usr/pppl/gmp/5.0.2 --with-mpfr=/usr/pppl/mpfr/3.0.1 Thread model: posix gcc version 4.6.0 (GCC) configure:4388: $? = 0 configure:4377: g++4 -V >&5 g++4: error: unrecognized option '-V' g++4: fatal error: no input files compilation terminated. configure:4388: $? = 1 configure:4377: g++4 -qversion >&5 g++4: error: unrecognized option '-qversion' g++4: fatal error: no input files compilation terminated. configure:4388: $? = 1 configure:4392: checking whether we are using the GNU C++ compiler configure:4411: g++4 -c conftest.cpp >&5 configure:4411: $? = 0 configure:4420: result: yes configure:4429: checking whether g++4 accepts -g configure:4449: g++4 -c -g conftest.cpp >&5 configure:4449: $? = 0 configure:4490: result: yes configure:4515: checking dependency style of g++4 configure:4625: result: gcc3 configure:4696: checking for ranlib configure:4712: found /usr/bin/ranlib configure:4723: result: ranlib configure:4748: checking for a sed that does not truncate output configure:4812: result: /bin/sed configure:4825: checking for ar configure:4843: found /usr/bin/ar configure:4855: result: /usr/bin/ar configure:4878: checking for perl configure:4896: found /usr/bin/perl configure:4908: result: /usr/bin/perl configure:4920: checking for gdb configure:4938: found /usr/bin/gdb configure:4951: result: /usr/bin/gdb configure:4975: checking dependency style of gcc4 configure:5083: result: gcc3 configure:5102: checking for diff -u configure:5110: result: yes configure:5122: checking for a supported version of gcc configure:5157: result: no (4) configure:5159: error: please use gcc >= 3.0 or clang >= 2.9 .......... ## ----------- ## ## confdefs.h. ## ## ----------- ## /* confdefs.h */ #define PACKAGE_NAME "Valgrind" #define PACKAGE_TARNAME "valgrind" #define PACKAGE_VERSION "3.7.0" #define PACKAGE_STRING "Valgrind 3.7.0" #define PACKAGE_BUGREPORT "val...@li..." #define PACKAGE_URL "" #define PACKAGE "valgrind" #define VERSION "3.7.0" #define GDB_PATH "/usr/bin/gdb" configure: exit 1 Thanks, Dave On May 17, 2012, at 10:29 AM, Tom Hughes wrote: > On 17/05/12 15:13, David Smith wrote: > >> Please help me diagnose the following configure error on a x86_64/Linux system. I searched google for solutions, but found none. The error seems or originate in [gcc-version] in configure.in. > > Well it looks like there is something very odd about your compiler because although it is gcc 4 autoconf seems to think it is behaving like gcc 3 in various ways. > > What is the output of "gcc --version"? > > Tom > > -- > Tom Hughes (to...@co...) > http://compton.nu/ |
|
From: Tom H. <to...@co...> - 2012-05-17 14:45:22
|
On 17/05/12 15:42, David Smith wrote: > Thanks for looking at this. Here's gcc --version: > > [sunfire02:~/packages/valgrind-3.7.0] % gcc --version > > gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-51) > Copyright (C) 2006 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > [sunfire02:~/packages/valgrind-3.7.0] % > > > Note that $CC is set to gcc4 (previous message). Both gcc and gcc4 are valid commands in the search path. Sorry, I meant gcc4 of course, but we've seen that anyway. What about "gcc4 -dumpversion"? Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: John R. <jr...@bi...> - 2012-05-17 14:45:39
|
> Please help me diagnose the following configure error on a x86_64/Linux system.
The error happens because the logic in ./configure does not like "gcc4" as the
name of the compiler. The logic confuses the trailing '4' as part of the
numerical version "4.6.0". But there is no dot '.' after the first '4',
and the logic cannot handle this.
> [sunfire02:~/packages/valgrind-3.7.0] % $CC --version
>
> gcc4 (GCC) 4.6.0
$ echo "gcc4 (GCC) 4.6.0" | sed 's/^[^0-9]*\([0-9.]*\).*$/\1/'
4
# Notice there is no dot '.' after the '4' above, because the '4'
# comes from "gcc4" and not from "4.6.0".
# Then notice that the 'case' logic in the configure script
# _does_ expect the dot ("notclang-4."):
case "${is_clang}-${gcc_version}" in
notclang-4.*)
The easiest work-around is to change "gcc4 " to "gcc " before any further
analysis:
gcc_version=`${CC} --version \
| head -n 1 \
| $SED 's/gcc[^ ]* /gcc /' \
| $SED 's/i686-apple-darwin10//' \
| $SED 's/i686-apple-darwin11//' \
| $SED 's/^[^0-9]*\([0-9.]*\).*$/\1/'`
--
|
|
From: Tom H. <to...@co...> - 2012-05-17 14:54:45
|
On 17/05/12 15:46, John Reiser wrote: >> Please help me diagnose the following configure error on a x86_64/Linux system. > > The error happens because the logic in ./configure does not like "gcc4" as the > name of the compiler. The logic confuses the trailing '4' as part of the > numerical version "4.6.0". But there is no dot '.' after the first '4', > and the logic cannot handle this. > >> [sunfire02:~/packages/valgrind-3.7.0] % $CC --version >> >> gcc4 (GCC) 4.6.0 > > $ echo "gcc4 (GCC) 4.6.0" | sed 's/^[^0-9]*\([0-9.]*\).*$/\1/' > 4 > # Notice there is no dot '.' after the '4' above, because the '4' > # comes from "gcc4" and not from "4.6.0". We don't try and parse that output unless "gcc -dumpversion" has failed to return a version number though, and in this case it will have done. Aha! I was looking at current svn... The 3.7.0 release does have the problem you describe, but somebody has fixed it in svn. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: David S. <drs...@gm...> - 2012-05-17 14:46:43
|
Hi Tom, [sunfire02:~/packages/valgrind-3.7.0] % gcc4 -dumpversion 4.6.0 [sunfire02:~/packages/valgrind-3.7.0] % -Dave On May 17, 2012, at 10:45 AM, Tom Hughes wrote: > On 17/05/12 15:42, David Smith wrote: > >> Thanks for looking at this. Here's gcc --version: >> >> [sunfire02:~/packages/valgrind-3.7.0] % gcc --version >> >> gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-51) >> Copyright (C) 2006 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >> >> [sunfire02:~/packages/valgrind-3.7.0] % >> >> >> Note that $CC is set to gcc4 (previous message). Both gcc and gcc4 are valid commands in the search path. > > Sorry, I meant gcc4 of course, but we've seen that anyway. > > What about "gcc4 -dumpversion"? > > Tom > > -- > Tom Hughes (to...@co...) > http://compton.nu/ |
|
From: Tom H. <to...@co...> - 2012-05-17 14:52:21
|
On 17/05/12 15:48, David Smith wrote:
> [sunfire02:~/packages/valgrind-3.7.0] % gcc4 -dumpversion
> 4.6.0
I'm baffled then. The configure script is basically doing this:
gcc_version=`${CC} -dumpversion 2>/dev/null`
and apparently gcc_version is getting set to "4" according to the
config.log output.
That is not acceptable as we are looking for 4.* but it also doesn't
make any sense based on the output you quoted above.
Tom
--
Tom Hughes (to...@co...)
http://compton.nu/
|
|
From: <la...@ii...> - 2013-09-03 08:25:14
|
Hello,
I want to do speculative loop paralleization on GPU.in which
i have to do dependency analysis and check if one iteration
of loop is reading some value and check that some other
iteration have written to same memory location general "read
after write" and "write after write" and "write after read"
detection.
I want to do it for GPU can i do it using valgrind tool
Plz Help
Thanks
|
|
From: <la...@ii...> - 2013-09-04 11:19:00
|
Hello,
I want to do speculative loop paralleization on GPU.in which
i have to do dependency analysis and check if one iteration
of loop is reading some value and check that some other
iteration have written to same memory location general "read
after write" and "write after write" and "write after read"
detection.
I want to do it for GPU can i do it using valgrind tool
Plz Help
Thanks
|
|
From: Dor B. D. <dor...@am...> - 2016-03-17 08:16:45
|
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp |
|
From: Shivakumar G <shi...@gm...> - 2016-10-15 01:43:15
|
Hi, I am trying to run valgrind on my executable which is of 32-bit. I am getting the following error: *valgrind <executable>* valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit) valgrind: <executable>: cannot execute binary file Couple of other logs which are useful: *file <executable>* <executable>: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, BuildID[sha1]=570302117aa12728043bc5263352ce95f637db35, not stripped *valgrind -d <executable>* --6455:1:debuglog DebugLog system started by Stage 1, level 1 logging requested --6455:1:launcher no tool requested, defaulting to 'memcheck' --6455:1:launcher no platform detected, defaulting platform to 'amd64-linux' --6455:1:launcher launching <path>/memcheck-amd64-linux --6455:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging requested Looks like valgrind launcher is automatically start 64bit execution, and hence throwing the above error. Is there a way I can run valgrind for my 32-bit image? However valgrind executable are built to support both 32-bit and 64 bit version. Regards, Shivakumar |
|
From: Kissami I. <kis...@gm...> - 2017-11-21 10:04:45
|
Hello, I was using valgrind on my Mac, but when I installed the last version of mac/os valgrind doesn't work. When i run ./configure I have this error message : please use gcc => 3.0 .... My gcc version is 4.2.1 clang version is 5.0 icc version is 15.0.2 Best regards, -- *Imad Kissami* Université Paris 13, Sorbonne Paris Cité IUT, département informatique 99, avenue Jean-Baptiste Clément F-93430 Villetaneuse, France kis...@gm... |
|
From: John R. <jr...@bi...> - 2017-11-21 14:01:38
|
*ALWAYS* give an appropriate Subject: when posting an inquiry. On 11/21/2017 1004Z, Kissami Imad wrote in a posting with no subject: > I was using valgrind on my Mac, but when I installed the last version of mac/os valgrind doesn't work. Which version of mac/os? Which version of valgrind? > When i run ./configure I have this error message : please use gcc => 3.0 .... > My gcc version is 4.2.1 > clang version is 5.0 > icc version is 15.0.2 > Look in config.log, which is created by running ./configure, such as: > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > It was created by Valgrind configure 3.13.0, which was > generated by GNU Autoconf 2.69. Invocation command line was > > $ ./configure --prefix=my_prefix Look for the section that detects compiler configuration, such as: > configure:3404: checking for gcc > configure:3420: found /usr/bin/gcc > configure:3431: result: gcc > configure:3660: checking for C compiler version > configure:3669: gcc --version >&5 > gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1) > Copyright (C) 2016 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > configure:3680: $? = 0 > configure:3669: gcc -v >&5 Copy+paste (into a reply to this posting) what you see in _your_ config.log. Copy+paste any other lines related to detection of a compiler. What clues do those messages give you? -- |
|
From: Kissami I. <kis...@gm...> - 2017-11-21 14:13:24
|
Hello, Thanks for your response, > Which version of mac/os? The latest one 10.13 high sierra, I checked in valgrind code source and I see that is no supported (this valgrind version support only 16.* versions) > Which version of valgrind? Valgrind version is 3.13.0 I modified the source code with adding same option for darwin 17.* and I success to install valgrind but when I used it for profiling I had this warning --55943-- WARNING: unhandled amd64-darwin syscall: unix:464 --55943-- You may be able to write your own handler. --55943-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --55943-- Nevertheless we consider this a bug. Please report --55943-- it at http://valgrind.org/support/bug_reports.html. --55943-- WARNING: unhandled amd64-darwin syscall: unix:464 --55943-- You may be able to write your own handler. --55943-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --55943-- Nevertheless we consider this a bug. Please report --55943-- it at http://valgrind.org/support/bug_reports.html. and the running of code is stopped. Best regards, Imad Kissami Post-Doc Université Paris 13, Sorbonne Paris Cité LAGA 99, av. J-B Clément 93430 Villetaneuse, France > Le 21 nov. 2017 à 15:01, John Reiser <jr...@bi...> a écrit : > > *ALWAYS* give an appropriate Subject: when posting an inquiry. > > On 11/21/2017 1004Z, Kissami Imad wrote in a posting with no subject: > >> I was using valgrind on my Mac, but when I installed the last version of mac/os valgrind doesn't work. > > Which version of mac/os? > Which version of valgrind? > >> When i run ./configure I have this error message : please use gcc => 3.0 .... >> My gcc version is 4.2.1 >> clang version is 5.0 >> icc version is 15.0.2 > > Look in config.log, which is created by running ./configure, such as: >> This file contains any messages produced by compilers while >> running configure, to aid debugging if configure makes a mistake. >> It was created by Valgrind configure 3.13.0, which was >> generated by GNU Autoconf 2.69. Invocation command line was >> $ ./configure --prefix=my_prefix > > Look for the section that detects compiler configuration, such as: >> configure:3404: checking for gcc >> configure:3420: found /usr/bin/gcc >> configure:3431: result: gcc >> configure:3660: checking for C compiler version >> configure:3669: gcc --version >&5 >> gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1) >> Copyright (C) 2016 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >> configure:3680: $? = 0 >> configure:3669: gcc -v >&5 > > Copy+paste (into a reply to this posting) what you see in _your_ config.log. > Copy+paste any other lines related to detection of a compiler. > What clues do those messages give you? > > -- > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: John R. <jr...@bi...> - 2017-11-21 14:32:42
|
On 11/21/2017 1413Z, Kissami Imad wrote: >> Which version of mac/os? > The latest one 10.13 high sierra, I checked in valgrind code source and I see that is no supported (this valgrind version support only 16.* versions) >> Which version of valgrind? > Valgrind version is 3.13.0 > > > I modified the source code with adding same option for darwin 17.* and I success to install valgrind but when I used it for profiling I had this warning > > --55943-- WARNING: unhandled amd64-darwin syscall: unix:464 > --55943-- You may be able to write your own handler. > --55943-- Read the file README_MISSING_SYSCALL_OR_IOCTL. > --55943-- Nevertheless we consider this a bug. Please report > --55943-- it at http://valgrind.org/support/bug_reports.html. > --55943-- WARNING: unhandled amd64-darwin syscall: unix:464 > --55943-- You may be able to write your own handler. > --55943-- Read the file README_MISSING_SYSCALL_OR_IOCTL. > --55943-- Nevertheless we consider this a bug. Please report > --55943-- it at http://valgrind.org/support/bug_reports.html. Using a web search engine, > No results found for unhandled amd64-darwin syscall: "unix:464" . therefore this is a system call that valgrind does not yet understand. Please follow the directions: report a bug, by visiting the given URL and entering the appropriate information. A good title would be MacOS: unhandled amd64-darwin syscall: unix:464 -- |
|
From: Zack W. <za...@pa...> - 2017-11-21 14:54:44
|
On Tue, Nov 21, 2017 at 9:32 AM, John Reiser <jr...@bi...> wrote: > > this is a system call that valgrind does not yet understand. > Please follow the directions: report a bug, by visiting the given URL > and entering the appropriate information. A good title would be > MacOS: unhandled amd64-darwin syscall: unix:464 Inspecting <https://github.com/opensource-apple/xnu/blob/master/bsd/kern/syscalls.master>, it looks like there are a whole bunch of new syscalls. They may have finally gotten around to implementing POSIX.1-2008 - 464 is an openat() variant. zw |
|
From: Jeffrey W. <nol...@gm...> - 2018-09-10 04:17:12
|
Hi Everyone, We are catching some Valgrind warnings when testing 32-bit x86 code. The warnings are: |
|
From: Dirk M. <dm...@gm...> - 2003-09-11 15:02:27
|
On Wednesday 10 September 2003 19:49, Kevin Olson wrote: > Is there any information on using VALGRIND with MPI programs ? Is there any problem when using VALGRIND with MPI applications? |
|
From: Ashley P. <as...@pi...> - 2003-09-11 15:49:01
|
On Thu, 2003-09-11 at 16:02, Dirk Mueller wrote: > On Wednesday 10 September 2003 19:49, Kevin Olson wrote: > > > Is there any information on using VALGRIND with MPI programs ? > > Is there any problem when using VALGRIND with MPI applications? I've done it for simple applications. There are some cosmetic problems to do with the way MPI works. Normally with the stdout and std from all processes are sent to the same place so it can be difficult reading the output. This is a generic MPI problem though. luckily using the --logfile= option to valgrind automatically prepends the pid though so it's easy to use this to sanitise the output. Ashley, |
|
From: Rob L. <ro...@te...> - 2003-09-15 14:44:42
|
On Wed, Sep 10, 2003 at 01:49:25PM -0400, Kevin Olson wrote: > Hello, > > Is there any information on using VALGRIND with MPI programs ? If your MPI implementation is MPICH, and your program takes command line arguments, there might be some problems, however a command like "mpirun /usr/bin/valgrind cpi" works. ==rob -- Rob Latham Chicago, IL USA |