16 Oct
2022
16 Oct
'22
9:59 p.m.
On Sun Oct 16 21:56:01 2022 +0000, **** wrote:
Zebediah Figura replied on the mailing list:
On 10/16/22 12:24, Rémi Bernon (@rbernon) wrote: > Valgrind support requires a fork, which I've published to https://gitlab.winehq.org/rbernon/valgrind. The fork implements loading DWARF debug info from PE files, instead of the old and broken upstream PDB support. I've tried to upstream these changes a long time ago but didn't receive any feedback. > > I think we could maybe consider keeping a fork, which I'm happy to maintain, as the changes aren't too large. We may want to investigate adding 32-on-64 support, which may require a bit more changes (to VEX specifically, because its amd64 guest doesn't support segment register manipulation). FWIW, I asked on #valgrind-dev, and was told that patches on the valgrind-developers mailing list may get forgotten, and that a more reliable path is to attach them to a bug at <https://bugs.kde.org/describecomponents.cgi?product=valgrind>. So there may be hope upstreaming these yet.
Which I did, at the time, here https://bugs.kde.org/show_bug.cgi?id=211031, without any sort of feedback from upstream either.