Yes, you are right, John.
The error message comes from glibc, but I didn't look in this direction.
For those coming after me with this task, below is the way to do this. To
cross-compile Valgrind 3.20.0 I used the following script:
export CC=arm-linux-gnueabihf-gcc
export CXX=arm-linux-gnueabihf-g++
export CCFLAGS="-mcpu=cortex-a8 -mfpu=neon"
export LDFLAGS="
-Wl,--rpath=/lib/glibc.2.23,--dynamic-linker=/lib/glibc.2.23/ld-linux-armhf.so.3"
./configure --host=armv7-linux-gnueabihyf
--target=armv7-linux-gnueabihf --prefix=/opt/FS_HDVR/opt
make
make install
When this finished successfully, I need to run the following command to
execute MyApp under Valgrind:
export VALGRIND_LIB=/opt/libexec/valgrind; /opt/bin/valgrind MyApp
Note that most probably (I am not sure) the glibc should correspond to the
cross-compiler in use.
Anyway, now I can run Valgrind with my application(s).
THANKS FOR THE HELP!
On Wed, 1 Mar 2023 at 00:02, John Reiser <jrei...@bitwagon.com> wrote:
> On 2/28/2023, Leon Pollak wrote:
> > I recall my previous mail about cross-compilation.
> > When i did exactly what is recommended, I managed to cross-compile.
> > The unexpected issue appeared when I run wvalgrind myappw:
> > FATAL: kernel too old
> > My kernel is 2.6.37 and seemed to be ok.
> > Is it final or can I do something further? Old Valgrind version, for
> example?
>
> The string "kernel too old" does not appear in the sources for valgrind
> 3.20.0,
> nor in the current 3.21.0, nor in previous 3.19.0. The substring "too old"
> likewise does not appear in the sources, except for configuration tests
> such as:
> ./configure: { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING:
> 'missing' script is too old or missing" >&5
>
> So, which software wrote "FATAL: kernel too old"? The utility 'strace'
> may help.
> Something like
> strace -f -o strace.out -e trace=execve,write,writev,pwrite,pwritev
> wvalgrind myappw
> where 'execve' tells the command line for a given PID, and the
> 'write,writev,...'
> trace various system calls which write to file descriptors, reporting the
> associated
> process id PID. Also run the 'strace' a second time with just the app,
> without valgrind.
> (By the way, what is the 'w' prefix and suffix in "wvalgrind myappw"?)
>
>
>
> _______________________________________________
> Valgrind-users mailing list
> Valgrind-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
