Re: [Valgrind-developers] Valgrind on ARM problems

[Julian S. <js...@ac...>]

ARMv7 is the baseline requirement, and realistically I don't think
v5 is likely to be supported.  It won't work as-is.

> Program terminated with signal 11, Segmentation fault.
> [New process 1071]
> #0  read_leb128 (data=0x403e074 <Address 0x403e074 out of bounds>,
> length_return=0x388bb5cc, sign=1413) at m_debuginfo/readdwarf.c:221
> 221	      byte = * data ++;

That said, it looks like your build segfaulted while reading Dwarf3
debug info.  Which has nothing to do with the v5 vs v7 question.  Not
sure why.  Which compiler produced the executable/shared object that
it was examining at the time?  Running Valgrind with -v will tell
you that.

J