Re: [Valgrind-developers] drd and amd64

[Tom H. <to...@co...>]

In message <e2e...@ma...> you wrote:

> This is the resulting output:
> 
> $ VALGRIND_LIB=.in_place coregrind/valgrind -d --tool=drd drd/tests/fp_race
> --3850:1:debuglog DebugLog system started by Stage 1, level 1 logging
> requested
> --3850:1:launcher tool 'drd' requested
> --3850:1:launcher selected platform 'amd64-linux'
> --3850:1:launcher launching .in_place/amd64-linux/drd

So it thinks it is launching a 64 bit tool...

> --3850:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging
> requested
> --3850:1:main     Welcome to Valgrind version 3.3.0.SVN debug logging
> --3850:1:main     Checking current stack is plausible
> --3850:1:main     Checking initial stack was noted
> --3850:1:main     Starting the address space manager
> --3850:1:main     Address space manager is running
> --3850:1:main     Starting the dynamic memory manager
> --3850:1:mallocfr newSuperblock at 0x4000000 (pszB 1048560) owner
> VALGRIND/tool
> --3850:1:main     Dynamic memory manager is running
> --3850:1:main     Getting stage1's name
> --3850:1:main     Get hardware capabilities ...
> --3850:1:main     ... arch = X86, hwcaps = x86-sse1-sse2

...but the tool actually seems to be a 32 bit one.

> --3850:1:main     Split up command line
> --3850:1:main     Preprocess command line opts
> --3850:1:main     Create initial image
> --3850:1:initimg  Loading client
> valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
> valgrind: drd/tests/fp_race: cannot execute binary file
> 
> It surprised me to see "arch = X86" in the output instead of "arch = AMD64"?

I think you will find that .in_place/amd64-linux/drd is a 32 bit
program - it should be a 64 bit one.

There must be something wrong with your build scripts I think.

Tom

-- 
Tom Hughes (to...@co...)
http://www.compton.nu/