|
From: Karl K. <mai...@bl...> - 2010-07-21 14:47:09
|
Hello,
I want to compile the Valgrind on x86 for PowerPC target. I use the toolchain
from Buildroot, and the compilation stops with the following error message:
/opt/toolchain/usr/include/a.out.h:1:25:
error: linux/a.out.h: No such file or directory
I guess, it comes from the disabled kernel option "BINFMT_AOUT: Kernel support
for a.out and ECOFF binaries". The problem is, that there is no kernel support
of a.out (HAVE_AOUT) for PowerPC.
Is there a way, to disable the a.out support of valgrind? On the target we
want to analyze ELF binaries only.
Best regards,
Charly
Symbol: BINFMT_AOUT [=n]
Prompt: Kernel support for a.out and ECOFF binaries
Defined at fs/Kconfig.binfmt:87
Depends on: HAVE_AOUT [=n]
Location:
-> Kernel options
Symbol: HAVE_AOUT [=n]
linux-2.6.33-rc6 $ find . -name a.out.h
./include/linux/a.out.h
./arch/arm/include/asm/a.out.h
./arch/x86/include/asm/a.out.h
./arch/alpha/include/asm/a.out.h
./arch/m68k/include/asm/a.out.h
linux-2.6.33-rc6 $
|
|
From: Julian S. <js...@ac...> - 2010-07-21 14:57:03
|
Valgrind has never supported a.out binaries. If a.out.h is being included, it must be for some other reason. J On Wednesday, July 21, 2010, Karl Krach wrote: > Hello, > > I want to compile the Valgrind on x86 for PowerPC target. I use the > toolchain from Buildroot, and the compilation stops with the following > error message: > > /opt/toolchain/usr/include/a.out.h:1:25: > error: linux/a.out.h: No such file or directory > > I guess, it comes from the disabled kernel option "BINFMT_AOUT: Kernel > support for a.out and ECOFF binaries". The problem is, that there is no > kernel support of a.out (HAVE_AOUT) for PowerPC. > > Is there a way, to disable the a.out support of valgrind? On the target we > want to analyze ELF binaries only. > > Best regards, > > Charly > > > > > Symbol: BINFMT_AOUT [=n] > Prompt: Kernel support for a.out and ECOFF binaries > Defined at fs/Kconfig.binfmt:87 > Depends on: HAVE_AOUT [=n] > Location: > -> Kernel options > > Symbol: HAVE_AOUT [=n] > > > > linux-2.6.33-rc6 $ find . -name a.out.h > ./include/linux/a.out.h > ./arch/arm/include/asm/a.out.h > ./arch/x86/include/asm/a.out.h > ./arch/alpha/include/asm/a.out.h > ./arch/m68k/include/asm/a.out.h > linux-2.6.33-rc6 $ > > > > --------------------------------------------------------------------------- > --- This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Bart V. A. <bva...@ac...> - 2010-07-21 14:59:11
|
On Wed, Jul 21, 2010 at 4:30 PM, Karl Krach <mai...@bl...>wrote: > Hello, > > I want to compile the Valgrind on x86 for PowerPC target. I use the > toolchain > from Buildroot, and the compilation stops with the following error message: > > /opt/toolchain/usr/include/a.out.h:1:25: > error: linux/a.out.h: No such file or directory > > I guess, it comes from the disabled kernel option "BINFMT_AOUT: Kernel > support > for a.out and ECOFF binaries". The problem is, that there is no kernel > support > of a.out (HAVE_AOUT) for PowerPC. > > Is there a way, to disable the a.out support of valgrind? On the target we > want to analyze ELF binaries only. > Valgrind uses <a.out.h> for the definition of 'struct nlist'. That definition is also present in <nlist.h>. Does your system have the header file /usr/include/nlist.h ? Bart. |
|
From: John R. <jr...@bi...> - 2010-07-21 15:15:55
|
> Is there a way, to disable the a.out support of valgrind? On the target we > want to analyze ELF binaries only. It seems that much of the reason that valgrind wants a.out.h is for the definition of "struct nlist", which is one format for storing information that is used for debugging. (DWARF3, etc., is another format.) The format for debug info is somewhat independent of the format for other parts of compiled code; both [E]COFF and ELF can have debug info that is formatted using "stabs". So: go to another system that does have a.out.h, extract the "struct nlist" (and associated typedefs and #defines, etc.) and put that code into a file (such as linux/a.out.h) where it will be picked up by valgrind. Or, put those definitions directly into file coregrind/m_debuginfo/readstabs.c, then edit the chain of #include which leads to a.out.h. -- |