valgrind on pure amd64 (64 bit system _only_)
What's state of valgrind port on pure amd64 system? Here, it core dumps upon linking both with clang and gcc47, with complaint that looks suspicious (expected i386 not X86_64 or something to that effect). -- View this message in context: http://freebsd.1045724.n5.nabble.com/valgrind-on-pure-amd64-64-bit-system-only-tp5762993.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: valgrind
Am Donnerstag, 31. Juli 2008 16:19:16 schrieb Andrea Venturoli: > > Or remove the line 'ONLY_FOR_ARCHS= i386' from the port Makefile, try it > > and see where it breaks. :-) I'm guessing it need some support code in > > the OS. > > That was more my question. There must be some OS support which FreeBSD > i386 has and FreeBSD amd64 has not. It was just curiosity, though. AFAIK it's not about OS-support for valgrind being required (but there is a module for freebsd which speeds up valgrind considerably), but about syscall-support. valgrind has/requires wrappers for all _possible_ syscalls to be able to implement it's memory-checker and some other functionality, and that table of callbacks and the callbacks themselves simply aren't implemented for amd64 (which has different syscalls/syscall parameters than i386). A porting effort is under way, as far as I recall a discussion on freebsd-hackers I had for a similar reason (the current valgrind that's in ports won't run on any 7.x, because the syscalls changed/were extended somewhat from the 6.x-series, and the table hasn't been adapted correspondingly), but the last time I pulled that porting effort (which is now about two months ago) and compiled it, valgrind was pretty much useless for me (even though it runs), because it couldn't deal with threads (i.e., the syscalls responsible for thread creation/management). Just check in the archives of freebsd-hackers, possibly what's currently present (someone did a tarball) is enough for your purposes. But, YMMV. -- Heiko Wundram ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: valgrind
Roland Smith wrote: Read http://valgrind.org/info/platforms.html, especially 'Porting Plans'. I had read this, but it dates back to Feb 2007; I just hoped it was obsolete :-( Or remove the line 'ONLY_FOR_ARCHS= i386' from the port Makefile, try it and see where it breaks. :-) I'm guessing it need some support code in the OS. That was more my question. There must be some OS support which FreeBSD i386 has and FreeBSD amd64 has not. It was just curiosity, though. bye & Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: valgrind
On Wed, Jul 30, 2008 at 05:12:39PM +0200, Andrea Venturoli wrote: > > ** Port marked as IGNORE: devel/valgrind: > is only for i386, while you are running amd64 > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > - devel/valgrind > > Same holds for valgrind-snapshot. > > On it's website I see it supports AMD64 on Linux, so I guess this is a > FreeBSD specific problem. > > Is there ongoing work to get this on amd64? > > Out of curiosity, what is the reason it does not work right now? Read http://valgrind.org/info/platforms.html, especially 'Porting Plans'. Or remove the line 'ONLY_FOR_ARCHS= i386' from the port Makefile, try it and see where it breaks. :-) I'm guessing it need some support code in the OS. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpPNMF8Dy4zL.pgp Description: PGP signature
valgrind
** Port marked as IGNORE: devel/valgrind: is only for i386, while you are running amd64 ** Listing the failed packages (-:ignored / *:skipped / !:failed) - devel/valgrind Same holds for valgrind-snapshot. On it's website I see it supports AMD64 on Linux, so I guess this is a FreeBSD specific problem. Is there ongoing work to get this on amd64? Out of curiosity, what is the reason it does not work right now? bye & Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Valgrind compilation failure on FreeBSD7.0 for i386
Hi, I would really like to use valgrind on my FreeBSD machine, but.. :-) -Yony >make ===> Building for valgrind-352_7 gmake all-recursive gmake[1]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable-352' Making all in include gmake[2]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/include' gmake all-am gmake[3]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/include' gmake[3]: Nothing to be done for `all-am'. gmake[3]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/include' gmake[2]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/include' Making all in coregrind gmake[2]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind' gmake all-recursive gmake[3]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind' Making all in x86 gmake[4]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind/x86' gmake all-am gmake[5]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind/x86' gmake[5]: Nothing to be done for `all-am'. gmake[5]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind/x86' gmake[4]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind/x86' Making all in demangle gmake[4]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind/demangle' gmake[4]: Nothing to be done for `all'. gmake[4]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind/demangle' Making all in . gmake[4]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable- 352/coregrind' if cc -DHAVE_CONFIG_H -I. -I. -I.. -I./demangle -I../include -I./x86 - DVG_LIBDIR="\"/usr/local/lib/valgrind"\"-Winline -Wall -Wshadow -O -fno-omit-frame-pointer -mpreferred-stack-boundary=2 -g -DELFSZ=32 -MT vg_mylibc.o -MD -MP -MF ".deps/vg_mylibc.Tpo" -c -o vg_mylibc.o vg_mylibc.c; \ then mv -f ".deps/vg_mylibc.Tpo" ".deps/vg_mylibc.Po"; else rm -f ".deps/vg_mylibc.Tpo"; exit 1; fi In file included from vg_include.h:49, from vg_mylibc.c:33: ../include/vg_skin.h:1230: warning: type qualifiers ignored on function return type vg_mylibc.c: In function 'vgPlain_kisemptysigset': vg_mylibc.c:65: warning: pointer targets in passing argument 1 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:65: warning: pointer targets in passing argument 2 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:65: warning: pointer targets in passing argument 4 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c: In function 'vgPlain_kisfullsigset': vg_mylibc.c:74: warning: pointer targets in passing argument 1 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:74: warning: pointer targets in passing argument 2 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:74: warning: pointer targets in passing argument 4 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c: In function 'vgPlain_ksigaddset_from_set': vg_mylibc.c:121: warning: pointer targets in passing argument 1 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:121: warning: pointer targets in passing argument 2 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:121: warning: pointer targets in passing argument 4 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c: In function 'vgPlain_ksigdelset_from_set': vg_mylibc.c:130: warning: pointer targets in passing argument 1 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:130: warning: pointer targets in passing argument 2 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:130: warning: pointer targets in passing argument 4 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c: In function 'vgPlain_ksignal': vg_mylibc.c:212: warning: pointer targets in passing argument 1 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:212: warning: pointer targets in passing argument 2 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:212: warning: pointer targets in passing argument 4 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c: In function 'vgPlain_exit': vg_mylibc.c:390: warning: pointer targets in passing argument 1 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:390: warning: pointer targets in passing argument 2 of 'vgPlain_core_assert_fail' differ in signedness vg_mylibc.c:390: warning: pointer targets in pass
