https://bugs.kde.org/show_bug.cgi?id=496468
--- Comment #7 from Satish Santhosh <satishs.kam...@gmail.com> ---
@Paul which linker flag are you talking about specifically? I can try and look
for this in the easybuild log file. In the mean time I also performed a build
from source and that works. So indeed the easybuild one is built incorrectly.
One built from source:
```
[satishk@tcn3 valgrind]$ objdump -p memcheck-amd64-linux
memcheck-amd64-linux: file format elf64-x86-64
Program Header:
LOAD off 0x0000000000000000 vaddr 0x0000000058000000 paddr
0x0000000058000000 align 2**12
filesz 0x0000000000000fd8 memsz 0x0000000000000fd8 flags r--
LOAD off 0x0000000000001000 vaddr 0x0000000058001000 paddr
0x0000000058001000 align 2**12
filesz 0x00000000001c7e6e memsz 0x00000000001c7e6e flags r-x
LOAD off 0x00000000001c9000 vaddr 0x00000000581c9000 paddr
0x00000000581c9000 align 2**12
filesz 0x00000000000ba94c memsz 0x00000000000ba94c flags r--
LOAD off 0x0000000000284000 vaddr 0x0000000058284000 paddr
0x0000000058284000 align 2**12
filesz 0x0000000000002bbc memsz 0x0000000001a0e450 flags rw-
NOTE off 0x0000000000000200 vaddr 0x0000000058000200 paddr
0x0000000058000200 align 2**3
filesz 0x0000000000000030 memsz 0x0000000000000030 flags r--
NOTE off 0x0000000000000230 vaddr 0x0000000058000230 paddr
0x0000000058000230 align 2**2
filesz 0x0000000000000da8 memsz 0x0000000000000da8 flags r--
0x6474e553 off 0x0000000000000200 vaddr 0x0000000058000200 paddr
0x0000000058000200 align 2**3
filesz 0x0000000000000030 memsz 0x0000000000000030 flags r--
STACK off 0x0000000000000000 vaddr 0x0000000000000000 paddr
0x0000000000000000 align 2**4
filesz 0x0000000000000000 memsz 0x0000000000000000 flags rw-
[satishk@tcn3 valgrind]$
```
Trying this out on the same executable:
```
[satishk@tcn3 bin]$ ./valgrind ~/temp/core_avx2.out
==367863== Memcheck, a memory error detector
==367863== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==367863== Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyright info
==367863== Command: /home/satishk/temp/core_avx2.out
==367863==
100 200 300 400 500 0 0 0
==367863==
==367863== HEAP SUMMARY:
==367863== in use at exit: 124 bytes in 4 blocks
==367863== total heap usage: 38 allocs, 34 frees, 9,050 bytes allocated
==367863==
==367863== LEAK SUMMARY:
==367863== definitely lost: 0 bytes in 0 blocks
==367863== indirectly lost: 0 bytes in 0 blocks
==367863== possibly lost: 0 bytes in 0 blocks
==367863== still reachable: 124 bytes in 4 blocks
==367863== suppressed: 0 bytes in 0 blocks
==367863== Rerun with --leak-check=full to see details of leaked memory
==367863==
==367863== For lists of detected and suppressed errors, rerun with: -s
==367863== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
[satishk@tcn3 bin]$
```
--
You are receiving this mail because:
You are watching all bug changes.
