I found the following problem in my real program for ARM CortexA8 with linux:
´*** glibc detected *** ./PRUssExternal: double free or corruption (top): 0x00024fe8 ***´
I am looking for this on the Internet and I have found that the most useful program to manage this is the Valgrind problem.
How to track double free error or corruption error in C ++ with gdb
Then I try to compile my system in cross-compilation with the following options in the configuration. I am using Valgrind 3.8.1
@ - virtual machine: ~ / Valgrind-3.8.1 $ CC = arm-cortexa8-linux-gnueabi-gcc CFLAGS = "- pipe -Os -mtune = cortex-a8 -march = armv7-a -mabi = aapcs-linux - msoft-float -I / opt / OSELAS.Toolchain-2011.11.3 / arm-cortexa8-linux-gnueabi / gcc-4.6.2-glibc-2.14.1-binutils -2.21.1a-kernel-2.6.39-sanitez / sysroot-arm-cortexa8-linux-gnueabi / usr / include "LDFLAGS =" - L / opt / OSELAS.Toolchain-2011.11.3 / arm-cortexa8-linux-gnueabi / gcc-4.6.2-glibc-2.14.1- binutils-2.21.1a-kernel-2.6.39-sanitez / sysroot-arm-cortexa8-linux-gnueabi / usr / lib ". / configure -prefix = / opt / valgrid -host = arm-cortexa8-linux-gnueabi -target = arm-none-linux-gnueabi -build = x86_64-ubuntu-linux
And the output of this configuration:
checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-cortexa8-linux-gnueabi-strip... arm-cortexa8-linux-gnueabi-strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking whether ln -s works... yes checking for arm-cortexa8-linux-gnueabi-gcc... arm-cortexa8-linux-gnueabi-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether arm-cortexa8-linux-gnueabi-gcc accepts -g... yes checking for arm-cortexa8-linux-gnueabi-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of arm-cortexa8-linux-gnueabi-gcc... gcc3 checking whether arm-cortexa8-linux-gnueabi-gcc and cc understand -c and -o together... yes checking how to run the C preprocessor... arm-cortexa8-linux-gnueabi-gcc -E checking for arm-cortexa8-linux-gnueabi-g++... arm-cortexa8-linux-gnueabi-g++ checking whether we are using the GNU C++ compiler... yes checking whether arm-cortexa8-linux-gnueabi-g++ accepts -g... yes checking dependency style of arm-cortexa8-linux-gnueabi-g++... gcc3 checking for arm-cortexa8-linux-gnueabi-ranlib... arm-cortexa8-linux-gnueabi-ranlib checking for a sed that does not truncate output... /bin/sed checking for ar... /usr/bin/ar checking for perl... /usr/bin/perl checking for gdb... /usr/bin/gdb checking dependency style of arm-cortexa8-linux-gnueabi-gcc... gcc3 checking for diff -u... yes checking for a supported version of gcc... ok (4.6.2) checking build system type... x86_64-ubuntu-linux-gnu checking host system type... arm-cortexa8-linux-gnueabi checking for a supported CPU... no (arm) configure: error: Unsupported host architecture. Sorry
The message “My problem” appears on the last line of this output, although I was looking for some information, and Cortexa8 is one of the supported plattaforms.
valgrind on ARM9?
For this reason, my question is whether my board is not supported, because the libraries that I use are incompatible or this may be another reason. Or in the other hand, I could compile valgrind without fear and skip this check.
thank you for your time
-Regards
Breci01010 ...
source share