tatref / linux-mem Goto Github PK

First, this tool like really great - stumbled across your blog post looking into memory fragmentation issues & this was exactly what I was looking for.

I compiled it on my Ubuntu VirtualBox VM (had to use rustup in nightly mode due to an error that appeared with the default rustc) and it ran successfully the first time I ran it, but the second time it seemed to get stuck in a loop & just chewed all the RAM until the VM froze. If I run it in strace I can see it seems to be doing the following over and over again:

read(4, "\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0"..., 8192) = 8192
read(4, "\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0"..., 8192) = 8192
read(4, "\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0"..., 8192) = 8192
read(4, "\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0"..., 8192) = 8192
read(4, "\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\200\0"..., 8192) = 8192

Anything I can do to try to debug further?