[valgrind] [Bug 453044] gbserver_tests failures in aarch64

2024-05-22 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=453044 --- Comment #6 from Jesus Checa --- (In reply to Paul Floyd from comment #4) > (In reply to Jesus Checa from comment #3) > > (In reply to Paul Floyd from comment #2) > > > Which version of gdb was this with? > > > > This

[valgrind] [Bug 453044] gbserver_tests failures in aarch64

2024-05-13 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=453044 --- Comment #3 from Jesus Checa --- (In reply to Paul Floyd from comment #2) > Which version of gdb was this with? This was gdb 8.2 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 467714] New: fdleak_* and rlimit tests fail when parent process has more than 64 descriptors opened.

2023-03-23 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=467714 Bug ID: 467714 Summary: fdleak_* and rlimit tests fail when parent process has more than 64 descriptors opened. Classification: Developer tools Product: valgrind Version: 3.19.0

[valgrind] [Bug 453087] New: [ppc64le] nlgone_abrt and nlpasssigalrm test failures in glibc-2.28

2022-04-27 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=453087 Bug ID: 453087 Summary: [ppc64le] nlgone_abrt and nlpasssigalrm test failures in glibc-2.28 Product: valgrind Version: 3.19.0 Platform: Other OS: Linux

[valgrind] [Bug 453055] New: shared_timed_mutex drd test fails with "Lock shared failed" message

2022-04-26 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=453055 Bug ID: 453055 Summary: shared_timed_mutex drd test fails with "Lock shared failed" message Product: valgrind Version: 3.19.0 Platform: Other OS: Linux

[valgrind] [Bug 453044] gbserver_tests failures in aarch64

2022-04-26 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=453044 --- Comment #1 from Jesus Checa --- Some additional info: The valgrind, kernel and glibc package versions are these: kernel-4.18.0-384.el8.aarch64 valgrind-3.19.0-1.el8.aarch64 glibc-2.28-197.el8.aarch64 -- You are receiving this mail because: You

[valgrind] [Bug 453044] New: gbserver_tests failures in aarch64

2022-04-26 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=453044 Bug ID: 453044 Summary: gbserver_tests failures in aarch64 Product: valgrind Version: 3.19.0 Platform: Other OS: Linux Status: REPORTED Severity: normal

[valgrind] [Bug 451827] [ppc64le] VEX temporary storage exhausted with several vbpermq instructions

2022-03-25 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=451827 --- Comment #4 from Jesus Checa --- Hi Carl, Thanks for the quick patch. I verified it with a fresh valgrind repo and all looks good now. FTR, these are the steps I followed for the verification: ``` $ gcc reproducer.c -o reproducer # This is the

[valgrind] [Bug 451827] New: [ppc64le] VEX temporary storage exhausted with several vbpermq instructions

2022-03-23 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=451827 Bug ID: 451827 Summary: [ppc64le] VEX temporary storage exhausted with several vbpermq instructions Product: valgrind Version: unspecified Platform: Other OS: Linu

[valgrind] [Bug 450962] helgrind reports false races for printfs using mempcpy manipulating FILE* state in glibc-2.26+

2022-02-28 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=450962 --- Comment #1 from Jesus Checa --- Created attachment 147188 --> https://bugs.kde.org/attachment.cgi?id=147188&action=edit Patch adding suppression + testcase Attaching a patch that adds the corresponding suppression and a testcase wi

[valgrind] [Bug 450962] New: helgrind reports false races for printfs using mempcpy manipulating FILE* state in glibc-2.26+

2022-02-28 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=450962 Bug ID: 450962 Summary: helgrind reports false races for printfs using mempcpy manipulating FILE* state in glibc-2.26+ Product: valgrind Version: unspecified Platform: Other

[valgrind] [Bug 447991] s390x: Valgrind indicates illegal instruction on wflrx

2022-01-17 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=447991 --- Comment #6 from Jesus Checa --- (In reply to Andreas Arnez from comment #3) > Right, m3 == 0 is not a valid format code. The z/Architecture Principle of > Operation states: > > The M3 field specifies the floating-point format.

[valgrind] [Bug 447991] s390x: Valgrind indicates illegal instruction on wflrx

2022-01-14 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=447991 Jesus Checa changed: What|Removed |Added CC||jch...@redhat.com --- Comment #2 from Jesus

[valgrind] [Bug 446123] New: Segfault when running a program that calls backtrace() [ppc64le]

2021-11-26 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=446123 Bug ID: 446123 Summary: Segfault when running a program that calls backtrace() [ppc64le] Product: valgrind Version: 3.18.1 Platform: Other OS: Linux St

[valgrind] [Bug 440670] New: unhandled ppc64le-linux syscall: 252 and unhandled ppc64le-linux syscall:253

2021-08-06 Thread Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=440670 Bug ID: 440670 Summary: unhandled ppc64le-linux syscall: 252 and unhandled ppc64le-linux syscall:253 Product: valgrind Version: unspecified Platform: Other OS: Lin