Hello!
On Wed, 7 Jun 2006, Tofik Suleymanov wrote:
I believe that it is possible to read contents of the memory used/utilized
by
a process (assuming right privileges).
Yes, procfs allows it to user with the process's UID (or root).
First i've tried to do this through procfs by reading 'mem
David Nugent wrote:
Tofik Suleymanov wrote:
Thank you for brief and altogether extensive explanation of the
case.The thing i wanted to do is to read let's say portions of memory
where .bss and .data block of a running program reside.
is that possible ?
Yes. Debuggers offer this functionality
Diomidis Spinellis wrote:
Tofik Suleymanov wrote:
Diomidis Spinellis wrote:
Tofik Suleymanov wrote:
The only way you're going to be able to read another processes
address space is in the kernel.Even a process running as root is
not able to read another process's data.
Incorrect; see this
Tofik Suleymanov wrote:
Diomidis Spinellis wrote:
Tofik Suleymanov wrote:
The only way you're going to be able to read another processes
address space is in the kernel.Even a process running as root is not
able to read another process's data.
Incorrect; see this example:
$ sed -e 's/this/
David Nugent wrote:
Tofik Suleymanov wrote:
Thank you for brief and altogether extensive explanation of the
case.The thing i wanted to do is to read let's say portions of memory
where .bss and .data block of a running program reside.
is that possible ?
Yes. Debuggers offer this functionality
Diomidis Spinellis wrote:
Tofik Suleymanov wrote:
The only way you're going to be able to read another processes
address space is in the kernel.Even a process running as root is not
able to read another process's data.
Incorrect; see this example:
$ sed -e 's/this/that/' &
[1] 87345
$ /bin
David Nugent wrote:
Tofik Suleymanov wrote:
Thank you for brief and altogether extensive explanation of the
case.The thing i wanted to do is to read let's say portions of memory
where .bss and .data block of a running program reside.
is that possible ?
Yes. Debuggers offer this functionality
Tofik Suleymanov wrote:
Thank you for brief and altogether extensive explanation of the
case.The thing i wanted to do is to read let's say portions of memory
where .bss and .data block of a running program reside.
is that possible ?
Yes. Debuggers offer this functionality, for example.
man 2
Tofik Suleymanov wrote:
The only way you're going to be able to read another processes
address space is in the kernel.Even a process running as root is not
able to read another process's data.
Incorrect; see this example:
$ sed -e 's/this/that/' &
[1] 87345
$ /bin/su
Password:
# dd if=/pro
James Riendeau wrote:
How are you defining "assuming right privileges"?
assuming uid 0
The only way you're going to be able to read another processes
address space is in the kernel.Even a process running as root is not
able to read another process's data.
how does gdb then reads for example
How are you defining "assuming right privileges"? The only way
you're going to be able to read another processes address space is in
the kernel. Even a process running as root is not able to read
another process's data. One of the principle responsibilities of the
OS is to manage the pri
Hello, folks
I believe that it is possible to read contents of the memory
used/utilized by a process (assuming right privileges).
First i've tried to do this through procfs by reading 'mem' property of
the given process, but no success.
Maybe there is another way of doing such things ?
Any clu
12 matches
Mail list logo
