|
From: Victor S. <vse...@pa...> - 2005-08-31 18:08:24
|
I have again tried to use valgrind on a 64 bit machine to grind a 32 bit
program, this time with 3.0.1.
It still fails.
I configure with:
./configure --prefix=/usr --build=i586-pc-linux-gnu
and it builds ok. However, the 'make check' fails with:
fpeflags.c:1: error: CPU you selected does not support x86-64
instruction set
After I install it , I try:
/usr/bin/valgrind hello
and I get this:
Process terminating with default action of signal 11 (SIGSEGV)
==25046== at 0x1B8EB054: open_verify (in /lib/ld-2.3.2.so)
==25046== by 0x1B8EB4E7: open_path (in /lib/ld-2.3.2.so)
==25046== by 0x1B8E9113: _dl_map_object (in /lib/ld-2.3.2.so)
==25046== by 0x1B8F0267: openaux (in /lib/ld-2.3.2.so)
==25046== by 0x1B8F0895: _dl_catch_error (in /lib/ld-2.3.2.so)
==25046== by 0x1B8EF75D: _dl_map_object_deps (in /lib/ld-2.3.2.so)
==25046== by 0x1B8E5881: dl_main (in /lib/ld-2.3.2.so)
==25046== by 0x1B8F3947: _dl_sysdep_start (in /lib/ld-2.3.2.so)
==25046== by 0x1B8E50B4: _dl_start (in /lib/ld-2.3.2.so)
==25046== by 0x1B8E4C66: (within /lib/ld-2.3.2.so)
==25046==
==25046== Process terminating with default action of signal 11 (SIGSEGV)
==25046== at 0x1B8FB87F: _vgw_freeres (vg_preloaded.c:58)
==25046== by 0x1B8EB4E7: open_path (in /lib/ld-2.3.2.so)
==25046== by 0x1B8E9113: _dl_map_object (in /lib/ld-2.3.2.so)
==25046== by 0x1B8F0267: openaux (in /lib/ld-2.3.2.so)
==25046== by 0x1B8F0895: _dl_catch_error (in /lib/ld-2.3.2.so)
==25046== by 0x1B8EF75D: _dl_map_object_deps (in /lib/ld-2.3.2.so)
==25046== by 0x1B8E5881: dl_main (in /lib/ld-2.3.2.so)
==25046== by 0x1B8F3947: _dl_sysdep_start (in /lib/ld-2.3.2.so)
==25046== by 0x1B8E50B4: _dl_start (in /lib/ld-2.3.2.so)
==25046== by 0x1B8E4C66: (within /lib/ld-2.3.2.so)
The same program, built for 64 bit, correctly grinds and finds errors,
with the 64-bit build of valgrind.
We currently build both kinds of programs on the Opteron box, as gcc
lets us compile them and gdb lets us debug them. It would be really good
to also be able to grind them.
If anyone knows how to do this, I would appreciate the guidance. If not,
I guess I just wait.
Victor Secarin
|
|
From: Tom H. <to...@co...> - 2005-08-31 18:24:57
|
In message <431...@pa...>
Victor Secarin <vse...@pa...> wrote:
> I configure with:
> ./configure --prefix=/usr --build=i586-pc-linux-gnu
> and it builds ok. However, the 'make check' fails with:
> fpeflags.c:1: error: CPU you selected does not support x86-64
> instruction set
I think you want --host not --build. I also wouldn't worry too much
about the tests as I have no idea if they work in a cross compile
environment like that.
> We currently build both kinds of programs on the Opteron box, as gcc
> lets us compile them and gdb lets us debug them. It would be really good
> to also be able to grind them.
We hope to provide much better support for this in the 3.1 release.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|