https://bugs.kde.org/show_bug.cgi?id=471032
Bug ID: 471032
Summary: s390x: helgrind/tests/tc11_XCHG.c expects code to be
at a low address space
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platfor
https://bugs.kde.org/show_bug.cgi?id=446123
--- Comment #2 from Tulio Magno Quites Machado Filho ---
Notice that glibc 2.35 changed the behavior of backtrace and this issue should
not happen anymore.
Anyway, the lack of vdso causes a difference of behavior when running on top
valgrind versus
https://bugs.kde.org/show_bug.cgi?id=434849
--- Comment #5 from Tulio Magno Quites Machado Filho ---
(In reply to Mark Wielaard from comment #4)
> Although in the case of glibc backtrace () we might also request a bug
> fix/workaround in glibc.
glibc's backtrace implementation has b
https://bugs.kde.org/show_bug.cgi?id=441506
Bug ID: 441506
Summary: powerpc: Instruct the assembler to generate POWER9
instructions
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=422683
Tulio Magno Quites Machado Filho changed:
What|Removed |Added
CC||tul...@quites.com.br
https://bugs.kde.org/show_bug.cgi?id=435665
--- Comment #13 from Tulio Magno Quites Machado Filho ---
(In reply to Carl Love from comment #12)
> The destination address for the paste instruction is always imapped into the
> current user address space, correct?
Correct. The address is
https://bugs.kde.org/show_bug.cgi?id=435665
--- Comment #8 from Tulio Magno Quites Machado Filho ---
(In reply to Julian Seward from comment #5)
> there's no way to tell Memcheck
> or any other tool, that the values in the destination area are
> derived from values in the source ar
https://bugs.kde.org/show_bug.cgi?id=434849
Bug ID: 434849
Summary: The vdso is not available when running on ppc64*
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severi
