[valgrind] Valgrind segfaults (RPI4, ARMv7 kernel)

[SmallAndSimple]

I am running an raspberry pi 4 with Arch Linux ARM, Armv7 kernel. I cannot seem to use Valgrind, it always segfaults on me. I am running valgrind-3.19.0-3. It segfaults with any executable, but for completeness: file main.cpp:
$this->bbcode_second_pass_code('', '
#include <iostream>

int main(void)
{
std::cout << "Hello, world!" << std::endl;
return 0;
}
')
Compile with:
$this->bbcode_second_pass_code('', 'g++ -ggdb -funwind-tables main.cpp')
Verify that ./a.out works fine:
$this->bbcode_second_pass_code('', '
rpi4 :: ~/tmp » ./a.out
hello, world!
')
Then valgrind:
$this->bbcode_second_pass_code('', '
rpi4 :: ~/tmp » valgrind -v ./a.out
==1548== Memcheck, a memory error detector
==1548== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==1548== Using Valgrind-3.19.0-8d3c8034b8-20220411 and LibVEX; rerun with -h for copyright info
==1548== Command: ./a.out
==1548==
--1548-- Valgrind options:
--1548-- -v
--1548-- Contents of /proc/version:
--1548-- Linux version 5.15.53-2-rpi-ARCH (builduser@leming) (armv7l-unknown-linux-gnueabihf-gcc (GCC) 12.1.0, GNU ld (GNU Binutils) 2.38) #1 SMP Wed Jul 13 13:20:34 MDT 2022
--1548--
--1548-- Arch and hwcaps: ARM, LittleEndian, ARMv8-neon-vfp
--1548-- Page sizes: currently 4096, max supported 4096
--1548-- Valgrind library directory: /usr/lib/valgrind
--1548-- Reading syms from /home/user/tmp/a.out
--1548-- Reading EXIDX entries: 1 available
--1548-- Reading EXIDX entries: 0 attempted, 0 successful
--1548-- Reading syms from /usr/lib/ld-linux-armhf.so.3
--1548-- Considering /usr/lib/debug/.build-id/07/2bb4cd73afd5d62040c7f3f482dbe17719bfea.debug ..
--1548-- .. build-id is valid
--1548-- Reading syms from /usr/lib/valgrind/memcheck-arm-linux
==1548== Downloading debug info for /usr/lib/valgrind/memcheck-arm-linux...
==1548== Server query failed: No such file or directory
--1548-- object doesn't have a symbol table
--1548-- object doesn't have a dynamic symbol table
--1548-- Reading EXIDX entries: 2145 available
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: ExtabEntryDecode: failed with error code: -10
==1548== Warning: whilst reading EXIDX: Implausible EXIDX last entry size 11167; using 1 instead.
--1548-- Reading EXIDX entries: 1879 attempted, 1833 successful
--1548-- Scheduler: using generic scheduler lock implementation.
--1548-- Reading suppressions file: /usr/lib/valgrind/default.supp
==1548== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-1548-by-user-on-???
==1548== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-1548-by-user-on-???
==1548== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-1548-by-user-on-???
==1548==
==1548== TO CONTROL THIS PROCESS USING vgdb (which you probably
==1548== don't want to do, unless you know exactly what you're doing,
==1548== or are doing some strange experiment):
==1548== /usr/lib/valgrind/../../bin/vgdb --pid=1548 ...command...
==1548==
==1548== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==1548== /path/to/gdb ./a.out
==1548== and then give GDB the following command
==1548== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=1548
==1548== --pid is optional if only one valgrind process is running
==1548==
==1548== Invalid write of size 4
==1548== at 0x401B13C: _dl_start (rtld.c:527)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0384 is on thread 1's stack
==1548== 120 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x401250C: _dl_setup_hash (dl-setup_hash.c:25)
==1548== by 0x401B79F: _dl_start_final (rtld.c:488)
==1548== by 0x401B79F: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0398 is on thread 1's stack
==1548== 8 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x4019708: _dl_sysdep_start (dl-sysdep.c:85)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0374 is on thread 1's stack
==1548== 32 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x4015A20: __GI___tunables_init (dl-tunables.c:279)
==1548== by 0x40198A3: _dl_sysdep_start (dl-sysdep.c:224)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf02fc is on thread 1's stack
==1548== 104 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x40126E4: _dl_sort_maps_init (dl-sort-maps.c:281)
==1548== by 0x40198A7: _dl_sysdep_start (dl-sysdep.c:227)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0374 is on thread 1's stack
==1548== 16 bytes below stack pointer
==1548==
--1548-- REDIR: 0x4022481 (ld-linux-armhf.so.3:strlen) redirected to 0x580da55c (???)
==1548== Invalid write of size 4
==1548== at 0x401FCD4: sbrk (sbrk.c:37)
==1548== by 0x40198DB: _dl_sysdep_start (dl-sysdep.c:241)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0368 is on thread 1's stack
==1548== 16 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x401BC40: dl_main (rtld.c:1320)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0154 is on thread 1's stack
==1548== 528 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x400C4A8: _dl_new_object (dl-object.c:59)
==1548== by 0x401C5D7: dl_main (rtld.c:1625)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0124 is on thread 1's stack
==1548== 48 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x400BF80: __minimal_calloc (dl-minimal-malloc.c:78)
==1548== by 0x400C503: calloc (rtld-malloc.h:44)
==1548== by 0x400C503: _dl_new_object (dl-object.c:92)
==1548== by 0x401C5D7: dl_main (rtld.c:1625)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0128 is on thread 1's stack
==1548== 16 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x400BE24: __minimal_malloc (dl-minimal-malloc.c:35)
==1548== by 0x400C503: calloc (rtld-malloc.h:44)
==1548== by 0x400C503: _dl_new_object (dl-object.c:92)
==1548== by 0x401C5D7: dl_main (rtld.c:1625)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0124 is on thread 1's stack
==1548== 24 bytes below stack pointer
==1548==
--1548-- REDIR: 0x4022fa0 (ld-linux-armhf.so.3:memcpy) redirected to 0x580da5c0 (???)
==1548== Invalid write of size 4
==1548== at 0x400C3D8: _dl_add_to_namespace_list (dl-object.c:31)
==1548== by 0x401C603: dl_main (rtld.c:1634)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0158 is on thread 1's stack
==1548== 16 bytes below stack pointer
==1548==
--1548-- REDIR: 0x4021d51 (ld-linux-armhf.so.3:strcmp) redirected to 0x580da6cc (???)
==1548== Invalid write of size 4
==1548== at 0x401250C: _dl_setup_hash (dl-setup_hash.c:25)
==1548== by 0x401CD07: dl_main (rtld.c:1693)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0168 is on thread 1's stack
==1548== 8 bytes below stack pointer
==1548==
==1548== Invalid write of size 4
==1548== at 0x4019DA0: _dl_discover_osversion (dl-sysdep.c:46)
==1548== by 0x401D233: dl_main (rtld.c:1721)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbeff64 is just below the stack ptr. To suppress, use: --workaround-gcc296-bugs=yes
==1548==
==1548==
==1548== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==1548== Access not within mapped region at address 0xBDBEFF64
==1548== at 0x4019DA0: _dl_discover_osversion (dl-sysdep.c:46)
==1548== by 0x401D233: dl_main (rtld.c:1721)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== If you believe this happened as a result of a stack
==1548== overflow in your program's main thread (unlikely but
==1548== possible), you can try to increase the size of the
==1548== main thread stack using the --main-stacksize= flag.
==1548== The main thread stack size used in this run was 8388608.
==1548==
==1548== HEAP SUMMARY:
==1548== in use at exit: 0 bytes in 0 blocks
==1548== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1548==
==1548== All heap blocks were freed -- no leaks are possible
==1548==
==1548== ERROR SUMMARY: 13 errors from 13 contexts (suppressed: 0 from 0)
==1548==
==1548== 1 errors in context 1 of 13:
==1548== Invalid write of size 4
==1548== at 0x4019DA0: _dl_discover_osversion (dl-sysdep.c:46)
==1548== by 0x401D233: dl_main (rtld.c:1721)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbeff64 is just below the stack ptr. To suppress, use: --workaround-gcc296-bugs=yes
==1548==
==1548==
==1548== 1 errors in context 2 of 13:
==1548== Invalid write of size 4
==1548== at 0x401250C: _dl_setup_hash (dl-setup_hash.c:25)
==1548== by 0x401CD07: dl_main (rtld.c:1693)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0168 is on thread 1's stack
==1548== 8 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 3 of 13:
==1548== Invalid write of size 4
==1548== at 0x400C3D8: _dl_add_to_namespace_list (dl-object.c:31)
==1548== by 0x401C603: dl_main (rtld.c:1634)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0158 is on thread 1's stack
==1548== 16 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 4 of 13:
==1548== Invalid write of size 4
==1548== at 0x400BE24: __minimal_malloc (dl-minimal-malloc.c:35)
==1548== by 0x400C503: calloc (rtld-malloc.h:44)
==1548== by 0x400C503: _dl_new_object (dl-object.c:92)
==1548== by 0x401C5D7: dl_main (rtld.c:1625)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0124 is on thread 1's stack
==1548== 24 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 5 of 13:
==1548== Invalid write of size 4
==1548== at 0x400BF80: __minimal_calloc (dl-minimal-malloc.c:78)
==1548== by 0x400C503: calloc (rtld-malloc.h:44)
==1548== by 0x400C503: _dl_new_object (dl-object.c:92)
==1548== by 0x401C5D7: dl_main (rtld.c:1625)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0128 is on thread 1's stack
==1548== 16 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 6 of 13:
==1548== Invalid write of size 4
==1548== at 0x400C4A8: _dl_new_object (dl-object.c:59)
==1548== by 0x401C5D7: dl_main (rtld.c:1625)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0124 is on thread 1's stack
==1548== 48 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 7 of 13:
==1548== Invalid write of size 4
==1548== at 0x401BC40: dl_main (rtld.c:1320)
==1548== by 0x401991B: _dl_sysdep_start (dl-sysdep.c:256)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0154 is on thread 1's stack
==1548== 528 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 8 of 13:
==1548== Invalid write of size 4
==1548== at 0x401FCD4: sbrk (sbrk.c:37)
==1548== by 0x40198DB: _dl_sysdep_start (dl-sysdep.c:241)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0368 is on thread 1's stack
==1548== 16 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 9 of 13:
==1548== Invalid write of size 4
==1548== at 0x40126E4: _dl_sort_maps_init (dl-sort-maps.c:281)
==1548== by 0x40198A7: _dl_sysdep_start (dl-sysdep.c:227)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0374 is on thread 1's stack
==1548== 16 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 10 of 13:
==1548== Invalid write of size 4
==1548== at 0x4015A20: __GI___tunables_init (dl-tunables.c:279)
==1548== by 0x40198A3: _dl_sysdep_start (dl-sysdep.c:224)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf02fc is on thread 1's stack
==1548== 104 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 11 of 13:
==1548== Invalid write of size 4
==1548== at 0x4019708: _dl_sysdep_start (dl-sysdep.c:85)
==1548== by 0x401B7E3: _dl_start_final (rtld.c:507)
==1548== by 0x401B7E3: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0374 is on thread 1's stack
==1548== 32 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 12 of 13:
==1548== Invalid write of size 4
==1548== at 0x401250C: _dl_setup_hash (dl-setup_hash.c:25)
==1548== by 0x401B79F: _dl_start_final (rtld.c:488)
==1548== by 0x401B79F: _dl_start (rtld.c:596)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0398 is on thread 1's stack
==1548== 8 bytes below stack pointer
==1548==
==1548==
==1548== 1 errors in context 13 of 13:
==1548== Invalid write of size 4
==1548== at 0x401B13C: _dl_start (rtld.c:527)
==1548== by 0x401A67F: ??? (in /usr/lib/ld-linux-armhf.so.3)
==1548== Address 0xbdbf0384 is on thread 1's stack
==1548== 120 bytes below stack pointer
==1548==
==1548== ERROR SUMMARY: 13 errors from 13 contexts (suppressed: 0 from 0)
[1] 1548 segmentation fault (core dumped) valgrind -v ./a.out
')
I also tested with valgrind-3.16.1-2-armv7h and valgrind-3.18.1-3-armv7h, with slightly different but mostly the same result. Could this be a bug or is it some mistake from my side?