|
From: Rich C. <Ric...@me...> - 2005-07-19 22:08:08
|
I'm testing on the x86_64 (amd64) platform and was wondering what the
expected behaviour of V should be in a mixed executabled environment.
I can have both 32-bit and 64-bit applications that I would want to run
V against. When I run V and it doesn't match the executable type it was
built for, like running the ELF-64 binary against an ELF-32 program,
V complains
valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
valgrind: do_exec(....) failed: Exec format error
Should V detect the ELF class at startup and use V code from
/usr/local/lib/valgrind or /usr/local/lib64/valgrind based on the ELF class ?
Rich
--
Rich Coe ric...@me...
General Electric Healthcare Technologies
Global Software Platforms, Computer Technology Team
|
|
From: Tom H. <to...@co...> - 2005-07-19 22:24:54
|
In message <20050719170607.6e5e4194@godzilla>
Rich Coe <Ric...@me...> wrote:
> I'm testing on the x86_64 (amd64) platform and was wondering what the
> expected behaviour of V should be in a mixed executabled environment.
>
> I can have both 32-bit and 64-bit applications that I would want to run
> V against. When I run V and it doesn't match the executable type it was
> built for, like running the ELF-64 binary against an ELF-32 program,
> V complains
> valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
> valgrind: do_exec(....) failed: Exec format error
>
> Should V detect the ELF class at startup and use V code from
> /usr/local/lib/valgrind or /usr/local/lib64/valgrind based on the ELF class ?
We don't yet have a solution for this - see the message Robert Walsh
posted a week or two back for some ideas on how we might approach it.
I suspect that in the initial release this won't be a solved problem.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|