Paul Floyd

dwarfdump -ka also complains *** DWARF CHECK: .debug_ranges: Address outside a valid .text range *** As far as I'm concerned this is not a Valgrind issue. The problem is either...

You need to find which tool is responsible for writing incorrect debuginfo. The problem doesn't seem to be in Valgrind.

I greatly truncated the output. The .debug_ranges message is there something like 13k times. On Arch Linux in VirtualBox Static hostname: archlinux Icon name: computer-vm Chassis: vm ���� Machine ID:...

I won't be able to help review the VEX code as it's the bit that I know the least. But I'm ready upstream and already done some testing and added...

We'll be discussing this on Friday (10th Feb 2023). See the valgrind developers mailing list.

"Valgrind community" usually just means Mark W, Julian S and myself (with Julian often being busy with other work). We discussed upstreaming at a recent video conf. Work is planned...

@rjiejie As far as I'm aware, no need to sign a license. Valgrind is GPLv2 (with the exception of the public headers which are BSD licensed to allow users to...

I can look, but VEX is the part that I've worked on the least.

@rjiejie if your patch is only for riscv, just go though the pull request process here and let @petrpavlu handle it. if you have something that is not riscv specific,...

If the patch is for riscv you need to submit it here.