[valgrind] [Bug 497078] New: vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7F 0x28 0x6F 0x54 0x16 0xFF 0x48 0x89 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0

2024-12-05 Thread Satish Santhosh
https://bugs.kde.org/show_bug.cgi?id=497078 Bug ID: 497078 Summary: vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7F 0x28 0x6F 0x54 0x16 0xFF 0x48 0x89 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR:

[valgrind] [Bug 496468] valgrind: mmap(0x400000, 8192) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments.

2024-11-27 Thread Satish Santhosh
https://bugs.kde.org/show_bug.cgi?id=496468 --- Comment #14 from Satish Santhosh --- Thanks Paul for checking this out. I will further try to debug as to what is happening within the Easybuild environment. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 496468] valgrind: mmap(0x400000, 8192) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments.

2024-11-26 Thread Satish Santhosh
https://bugs.kde.org/show_bug.cgi?id=496468 --- Comment #11 from Satish Santhosh --- It indeed may be using the gold linker within the Easybuild env. Are you saying that valgrind should NOT be linked with ld.gold at all? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 496468] valgrind: mmap(0x400000, 8192) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments.

2024-11-25 Thread Satish Santhosh
https://bugs.kde.org/show_bug.cgi?id=496468 --- Comment #9 from Satish Santhosh --- The easybuild log regarding the linker: ``` checking if the linker accepts -Wl,--image-base... no checking if the linker accepts -Wl,-Ttext-segment... no configure: ld -Ttext used, need to strip build-id NOTEs

[valgrind] [Bug 496468] valgrind: mmap(0x400000, 8192) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments.

2024-11-25 Thread Satish Santhosh
https://bugs.kde.org/show_bug.cgi?id=496468 --- Comment #7 from Satish Santhosh --- @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

[valgrind] [Bug 496468] valgrind: mmap(0x400000, 8192) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments.

2024-11-25 Thread Satish Santhosh
https://bugs.kde.org/show_bug.cgi?id=496468 --- Comment #5 from Satish Santhosh --- ``` [satishk@tcn3 ~]$ objdump -p ~/.local/easybuild/RHEL9/2024/software/Valgrind/3.24.0-gompi-2024a/libexec/valgrind/memcheck-amd64-linux /home/satishk/.local/easybuild/RHEL9/2024/software/Valgrind/3.24.0

[valgrind] [Bug 496468] valgrind: mmap(0x400000, 8192) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments.

2024-11-24 Thread Satish Santhosh
https://bugs.kde.org/show_bug.cgi?id=496468 --- Comment #3 from Satish Santhosh --- Created attachment 176088 --> https://bugs.kde.org/attachment.cgi?id=176088&action=edit Requested stderr into a file Sorry for the late reply. PFA . -- You are receiving this mail because: You are w

[valgrind] [Bug 496468] New: valgrind: mmap(0x400000, 8192) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments.

2024-11-19 Thread Satish Santhosh
https://bugs.kde.org/show_bug.cgi?id=496468 Bug ID: 496468 Summary: valgrind: mmap(0x40, 8192) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or