I've got a request for a 'trivial' kdb feature: something 'grep'-like for searching system memory.
I've got some corrupted system memory and I can't tell who did it, so I'd like to be able to search all of system memory and see if I can find anything pointing at it. Hopefully, If I can see who is pointing at my corrupt ram, I'd have a good idea of where to look for a bug. Right now, it feels more like snark-hunting. Comments? Suggestions? --linas
