This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
RFA: procfs.c: init_procfs_ops should set procfs_ops.to_has_[all]_memory
- To: gdb-patches at sourceware dot cygnus dot com
- Subject: RFA: procfs.c: init_procfs_ops should set procfs_ops.to_has_[all]_memory
- From: "Peter.Schauer" <Peter dot Schauer at regent dot e-technik dot tu-muenchen dot de>
- Date: Mon, 27 Mar 2000 17:38:15 MET DST
I am pretty sure that this is caused by some accidental deletion, but
procfs.c:init_procfs_ops no longer sets procfs_ops.to_has_memory and
procfs_ops.to_has_all_memory.
I noticed it when issuing an `i target' command on Solaris with a running
executable:
(gdb) i target
Symbols from "/home2/pes/gnu/gdb/gdbnd/solx86/gdb/testsuite/gdb.base/run".
Local exec file:
`/home2/pes/gnu/gdb/gdbnd/solx86/gdb/testsuite/gdb.base/run',
file type elf32-i386.
Entry point: 0x8048a34
0x080480f4 - 0x08048105 is .interp
.
.
After applying the patch below I get the more familiar:
(gdb) i target
Symbols from "/home2/pes/gnu/gdb/gdbnd/solx86/gdb/testsuite/gdb.base/run".
Unix /proc child process:
Using the running image of child LWP 1 via /proc.
While running this, GDB does not access memory from...
Local exec file:
`/home2/pes/gnu/gdb/gdbnd/solx86/gdb/testsuite/gdb.base/run',
file type elf32-i386.
Entry point: 0x8048a34
0x080480f4 - 0x08048105 is .interp
.
.
2000-03-27 Peter Schauer <pes@regent.e-technik.tu-muenchen.de>
* procfs.c (init_procfs_ops): Set procfs_ops.to_has_memory and
procfs_ops.to_has_all_memory to 1.
--- gdb/procfs.c.orig Wed Mar 1 21:54:05 2000
+++ gdb/procfs.c Sun Mar 26 22:07:31 2000
@@ -154,6 +154,8 @@ init_procfs_ops ()
procfs_ops.to_thread_alive = procfs_thread_alive;
procfs_ops.to_pid_to_str = procfs_pid_to_str;
+ procfs_ops.to_has_all_memory = 1;
+ procfs_ops.to_has_memory = 1;
procfs_ops.to_has_execution = 1;
procfs_ops.to_has_stack = 1;
procfs_ops.to_has_registers = 1;
--
Peter Schauer pes@regent.e-technik.tu-muenchen.de