I’m currently working on developing an implementation of the Concurrent Atomistic-Continuum method using C++ and CUDA to accelerate calculations. A need arose to use valgrind for debugging some memory issues. I currently run Artix Linux and it turns out that both Artix Linux and Arch Linux have fully removed all debug packages from their repositories and have swapped over to a debuginfod style system. On my system, said debuginfod was working with gdb but not with valgrind . In particular I was missing the debug symbols for glibc which prevented valgrind from working at all. I had to try a few things before I got it working so I want to share how I did. I also want to mention an issue I ran into if any guys from Artix Linux ever end up reading this post.
Book Review: GPU-Accelerated Computing with Python 3 and CUDA