Post #2502428
2026-04-03 11:20 UTC
@paulf@mastodon.bsd.cafe @stsquad@mastodon.org.uk The parts I was thinking of sharing aren't the CPU part; I was more thinking about the syscall and /proc emulation specific to the user-mode side of things. (I hadn't realised DynamoRio was still around).
Replies (1)
-
@paulf@mastodon.bsd.cafe 2026-04-03 11:33
@penguin42@mastodon.org.uk @stsquad@mastodon.org.uk syscall wrappers in Valgrind are a fairly big part of the code, but mostly they don't do much, just check the arguments and check pointers to memory that the syscalls read or write. And do some fd checking / monitoring. It's only process/CPU syscalls where Valgrind has to do a lot more intrusive work. For /proc and sysctls we do virtualise a few but for most of them we can just pass through to the originals. ELF (and macho) and DWARF readers are also sources of headaches for us.