Thank you, John for your humor...:-))) This is ARMv7 (Cortex-A8) the TI TMS320DM8148 CPU with 1GB RAM and there is no chance to switch to something else. The Valgrind manual says that it supports Linux 2.6.31 and younger, 2.6.37 seems to be younger...:-) Why are you so pessimistic...:-)
On Tue, 28 Feb 2023 at 22:44, 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? > Stop. Give it up. Find something else to do. If this is your job, > then find a new job as soon as you can, so that you can quit this insanity. > > Even OpenWRT runs Linux 5.11. It seems likely that your environment > is some ARM (v4 or v5) embedded system that has an app with a horrendous > bug > that you are trying to find and fix. Trying to do this natively, running > such an old kernel and probably with severely limited RAM, is insane. > > Get a 4GB or 8GB Raspberry Pi running a current Debian or Fedora Linux, > and debug the app there. The Pi has GPIO, USB, Ethernet, camera, and > dot-matrix display interfaces. If there are other sensors on your > device, then you should have hardware adapters so that they can use > USB interfacing, so that you *can* use a Pi as a real-time development > environment. If your management won't spend the time or money to > make or procure such adapters for the sensors, then there is *NO* hope. > > > > _______________________________________________ > 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
