Bug 105169 - valgrind: wrong ELF executable class (e.g. 32-bit instead of 64-bit)
Summary: valgrind: wrong ELF executable class (e.g. 32-bit instead of 64-bit)
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: ConsoleApps (show other bugs)
Version: Beta 1
Hardware: x86-64 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Dirk Mueller
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-17 12:41 UTC by Ulrich Windl
Modified: 2005-11-10 10:16 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2005-08-17 12:41:06 UTC
When trying to trace a 32-bit program on a 2.8GHz Xeon machine, valgrind
complains about
valgrind: wrong ELF executable class (e.g. 32-bit instead of 64-bit)
valgrind: do_exec(program_name) failed: Exec format error

program_name is a "ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for
GNU/Linux 2.2.0, dynamically linked..."

The programs runs fine without valgrind however.
Comment 1 Stephan Kulow 2005-08-17 12:54:06 UTC
with any program? Can you attach it? 
Comment 2 Ulrich Windl 2005-08-17 13:05:33 UTC
Not with any program: "valgrind /bin/bash" (ELF 64-bit executable, AMD x86-64,
...) seems to work. Maybe for any non-SuSE program? ;-)
OK, I had to search a while for a non-64 bit program from SuSE, but I found one:
/sbin/activate from the lilo-22.7-2 package produces the same error message.
Comment 3 Dirk Mueller 2005-08-17 14:05:56 UTC
valgrind doesn't have biarch support, so install the 32 bit version for 
tracing 32 bit apps.  
Comment 4 Ulrich Windl 2005-08-18 06:17:18 UTC
I have installed all versions of valgrind that were on the DVD. So it's you
fault, no my fault.
Comment 5 Dirk Mueller 2005-08-22 12:37:31 UTC
use the valgrind2 package.   
  
there is currently no biarch support in valgrind, so its not something that we  
can solve as part of the packaging process.   
  
it might get fixed for valgrind 3.1, but thats a bit too far in the future for 
SL10.  
Comment 6 Dirk Mueller 2005-09-17 08:25:59 UTC
post 10.0 
Comment 7 Dirk Mueller 2005-10-17 07:35:43 UTC
might not even get fixed in valgrind 3.1. 
Comment 8 Dirk Mueller 2005-11-10 10:15:37 UTC
ok..
Comment 9 Dirk Mueller 2005-11-10 10:16:43 UTC
updated supplementary / 10.1 with valgrind 3.1 which fixes cross-execution.