Memory scanning under Linux

On Thu, 08 Jun 2006 15:22:45 GMT, Tauno Voipio staggered into the Black Sun and said:

It might simplify things if you'd be more specific about what this app was going to be used for. When you're dealing with this kind of thing, typically Details Count, and you haven't provided very many details here.

Run "swapoff -a" before scanning? Still,dev-mem contains a lot of stuff besides memory used by various processes, like the 64K BIOS on an x86. And if there's any reasonable amount of RAM on the machine, it'll take 10-15 seconds to do something like "stringsdev-mem grep crud".

True. Howard may have a difficult time getting the map for a particular process's memory from userspace. proc-$PID-maps provides logical data, not physical data, given that every process seems to have its map start at 0x08048000 here on my laptop. There may be a way to do this, but it's highly probable there's an easier way to do whatever it is that you really want to do.

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL