Re: Accessing proc/memory

It seems that the kernel doesn't let you access a processes memory in that way. That's arguably A Good Thing.

Why do you want to "cheat"? Why do you think "changing memory of programs at runtime" is a good idea? This sounds much like an XY Problem.

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Comment on Re: Accessing proc/memory

Replies are listed 'Best First'.
Re^2: Accessing proc/memory by Anonymous Monk on Jul 31, 2006 at 23:40 UTC
It's only an XY problem if I do not explain the greater goal, but which I did. Have you never cheated in computer games? It's either hexediting savefiles or messing with the memory in a debugger. That's what brought me to Turbo Pascal and programming in general in the first place! I don't believe that the kernel doesn't let me do anything I want to do. I have su privileges and am not afraid to use them. If accessing memory is possible in DOS, Win98 and Win2k, so it bleeding well be in Linux. These mem files aren't just lying around /proc because they look pretty, you see.	[reply]
Re^3: Accessing proc/memory by shmem (Chancellor) on Aug 01, 2006 at 00:15 UTC
It's only an XY problem if I do not explain the greater goal, but which I did. Didnt see it. Have you never cheated in computer games? Erm... no. I don't do computer games. I don't believe that the kernel doesn't let me do anything I want to do. Well, if you haven't selinux turned on, that is. Then there are fences which UID 0 cannot pass either. Ah, and beliefs.. talking of them - confronted with facts, your belief is as good as mine ;-) --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply]