Program to debug memory leaks on armv4 architecture [closed] - c

Question

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I have a linux device that has armv4 CPU, and develop C code on it. I would like to debug my code via valgrind. However, I get a message saying that valgrind does not support armv4l. I wonder if there would be a way to suppress the error or what could be an alternative debugging package to analyze memory leaks?
Here is how I try to install the valgrind
ts7500:/home# tar -xjf valgrind-3.8.1.tar.bz2
ts7500:/home# cd valgrind-3.8.1
ts7500:/home/valgrind-3.8.1# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for gcc... 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... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ranlib... 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 gcc... gcc3
checking for diff -u... yes
checking for a supported version of gcc... ok (4.3.2)
checking build system type... armv4l-unknown-linux-gnu
checking host system type... armv4l-unknown-linux-gnu
checking for a supported CPU... no (armv4l)
configure: error: Unsupported host architecture. Sorry
ts7500:/home/valgrind-3.8.1#